[PATCH 08/10] net/farady: Support NCSI mode
benh at kernel.crashing.org
Fri Jul 1 21:26:56 AEST 2016
On Thu, 2016-06-30 at 23:35 +0930, Joel Stanley wrote:
> We get this message whenever the device is brought up or down. This
> includes when the host reboots, filling up the bmc's kernel logs.
> However, when we had the timer race it was the only way to know what
> was going on. Can we detect when it's the host bringing the device
> down opposed to an "ifconfig up" failing to bring it up?
What would be nice would be if we could mirror that into the "carrier"
state of the interface (which normally corresponds to the PHY link
The problem however is that when the carrier is off, the network stack
will ditch packets, which doen't work for us since we still need to
talk NSCI ...
I'm thinking we should create some netdev flags so that the generic
link monitor stops bringing it down in that case. That way we can
set the carrier and eixsting stuff that knows how to read and interpret
it will work.
More information about the openbmc