This patch is supposed to fix this behaviour. If LanWake is 0, the
function now returns 0. Thus ethtool correctly reports "Wake-on: d".
Can you turn it into a DMI controlled one (something like
drivers/net/ethernet/marvell/skge.c use of dmi_check_system) in order to
avoid a global change of behavior ?
Btw it's probably time to emit some warning during driver probe if wol
bits are not consistent with LanWake.
--
Ueimor