From: Andrew Lunn <andrew@lunn•ch>
To: Russell King - ARM Linux admin <linux@armlinux•org.uk>
Cc: Florian Fainelli <f.fainelli@gmail•com>,
Vladimir Oltean <olteanv@gmail•com>,
Heiner Kallweit <hkallweit1@gmail•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
Ioana Ciornei <ioana.ciornei@nxp•com>
Subject: Re: Cutting the link on ndo_stop - phy_stop or phy_disconnect?
Date: Tue, 4 Jun 2019 23:56:18 +0200 [thread overview]
Message-ID: <20190604215618.GX19627@lunn.ch> (raw)
In-Reply-To: <20190604214845.wlelh454qfnrs42s@shell.armlinux.org.uk>
> For a switch, there are four stages, not two:
Agreed.
> 1. The out-of-reset state, which from what I've seen seems to be to
> behave like a dumb switch.
For the Marvell Switches, there is a pin you can strap to control
this, NO_CPU. If you say there is no CPU, it will power up in dumb
switch mode, and potentially bring your network down with a broadcast
storm because of loops.
So yes, you need to think about this at all four stages, and make sure
your hardware engineer is also on board.
Andrew
next prev parent reply other threads:[~2019-06-04 21:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 19:58 Cutting the link on ndo_stop - phy_stop or phy_disconnect? Vladimir Oltean
2019-06-04 20:07 ` Andrew Lunn
2019-06-04 20:42 ` Vladimir Oltean
2019-06-04 20:55 ` Heiner Kallweit
2019-06-04 21:23 ` Vladimir Oltean
2019-06-04 20:57 ` Florian Fainelli
2019-06-04 21:26 ` Vladimir Oltean
2019-06-04 21:12 ` Andrew Lunn
2019-06-04 21:29 ` Vladimir Oltean
2019-06-04 21:37 ` Florian Fainelli
2019-06-04 21:48 ` Russell King - ARM Linux admin
2019-06-04 21:56 ` Andrew Lunn [this message]
2019-06-04 22:03 ` Vladimir Oltean
2019-06-04 22:16 ` Russell King - ARM Linux admin
2019-06-04 22:44 ` Vladimir Oltean
2019-06-04 22:59 ` Russell King - ARM Linux admin
2019-06-04 23:03 ` Vladimir Oltean
2019-06-04 23:24 ` Russell King - ARM Linux admin
2019-06-04 23:46 ` Vladimir Oltean
2019-06-05 0:04 ` Russell King - ARM Linux admin
2019-06-05 3:06 ` Florian Fainelli
2019-06-05 8:27 ` Vladimir Oltean
2019-06-05 9:30 ` Russell King - ARM Linux admin
2019-06-05 11:19 ` Vladimir Oltean
2019-06-05 12:16 ` Russell King - ARM Linux admin
2019-06-05 12:35 ` Russell King - ARM Linux admin
2019-06-04 20:25 ` Florian Fainelli
2019-06-04 21:36 ` Russell King - ARM Linux admin
2019-06-05 2:25 ` Florian Fainelli
2019-06-05 8:45 ` Russell King - ARM Linux admin
2019-06-05 18:01 ` Florian Fainelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190604215618.GX19627@lunn.ch \
--to=andrew@lunn$(echo .)ch \
--cc=f.fainelli@gmail$(echo .)com \
--cc=hkallweit1@gmail$(echo .)com \
--cc=ioana.ciornei@nxp$(echo .)com \
--cc=linux@armlinux$(echo .)org.uk \
--cc=netdev@vger$(echo .)kernel.org \
--cc=olteanv@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox