Re: Bug#690845: ethtool: incorrect WoL detection on Broadcom NX II rev < 12

[Ben Hutchings <ben@decadent.org.uk>]

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

On Mon, 2012-10-22 at 15:54 -0700, Michael Chan wrote:
> On Mon, 2012-10-22 at 10:52 +0300, Teodor MICU wrote:
> > 08:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
> > Gigabit Ethernet (rev 11)
> 
> It is 5708 B1, and due to some hardware limitations, ethtool initiated
> WoL is not supported.
[...]

Well we knew that much!  Is the problem that the system firmware 'owns'
the WoL control registers so the host can't safely change them?  Is it
possible to *read* the WoL configuration, if not to change it?

(If even that is not possible, the correct thing to do might be for
ETHTOOL_GWOL to return 'don't know' (EOPNOTSUPP) for this device.  But
since ethtool_ops::get_wol (and various other operations) can't return
an error, that would require you to define a separate instance of
ethtool_ops with get_wol = NULL.  I should look at fixing that...)

Ben.

-- 
Ben Hutchings
Humour is the best antidote to reality.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]