Corinna Vinschen <vinsc...@redhat.com> : [...] > 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 -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
