Stephen Hemminger wrote:
On Fri, 03 Nov 2006 16:02:30 -0800 (PST)
David Miller <[EMAIL PROTECTED]> wrote:
From: Jeff Garzik <[EMAIL PROTECTED]>
Date: Fri, 03 Nov 2006 18:51:25 -0500
The purpose of WOL is being able to turn on a system remotely, if it is
in a power-off or sleep state.
So, if the system is -on- and the interface is down and/or driver is
unloaded, are you saying WOL is a problem somehow?
Stephen is saying that if you down an interface, it should disable
that WoL functionality.
I guess you can argue that, like IP addresses, this WoL thing is an
attribute of the "system".
Looking harder. The semantic needs to be WOL is okay if driver is loaded
and device is up or down. But the default for WOL should be disabled until
enabled by ethtool (or parameter).
Since this is enabled already in the BIOSes for most systems (or disabled, and
switcheable by the user), I'd say we can let the driver handle the default (on for most
cards) already. The BIOS can also handle a WoL call after a (long) powerfailure, before
the OS boots, so disabling it in the OS would be quite useless in that case: the BIOS
would override it anyway.
Doesn't sound like a problem you can solve in the driver layer...
Cheers,
Auke
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
