lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 21 Jul 2009 20:56:45 -0700 (PDT) From: David Miller <davem@...emloft.net> To: alexander.duyck@...il.com Cc: andy@...yhouse.net, john.ronciak@...el.com, netdev@...r.kernel.org, jeffrey.t.kirsher@...el.com, jesse.brandeburg@...el.com, bruce.w.allan@...el.com, peter.p.waskiewicz.jr@...el.com, stable@...nel.org Subject: Re: [PATCH] igb/e1000e/e1000/e100: make wol usable From: Alexander Duyck <alexander.duyck@...il.com> Date: Tue, 21 Jul 2009 20:25:31 -0700 > My understanding was that the can_wakeup was supposed to be > initialized by pci_pm_init or platform_pci_wakeup_init based on the > pci-e capabilities. Is this not the case? It seems like this is > where you should be looking to determine why the the can_wakeup isn't > being initialized correctly. > > The patch below won't solve the problem either. The problem is that > the can_wakeup value is being disabled when the EEPROM doesn't support > WOL. > > If you have to do this in the drivers, then my suggestion is to take a > look at how ixgbe is doing it. You essentially need to initialize > can_wakeup to true, and then set the should_wakeup attribute based on > the EEPROM setting or via ethtool. This way you can still toggle the > should_wakeup option without being blocked by the EEPROM disabling it. It looks like the approach needs to be worked out still, so I'm tossing these patches from patchwork. Let me know when a more final fix is ready. Thanks. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists