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
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ff0cea8c-5aed-431c-a525-210fd8c10c31@lunn.ch>
Date: Tue, 27 Feb 2024 02:38:40 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Raju Lakkaraju <Raju.Lakkaraju@...rochip.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
	linux-kernel@...r.kernel.org, bryan.whitehead@...rochip.com,
	richardcochran@...il.com, UNGLinuxDriver@...rochip.com
Subject: Re: [PATCH net 1/3] net: lan743x: disable WOL upon resume to restore
 full data path operation

On Mon, Feb 26, 2024 at 01:39:32PM +0530, Raju Lakkaraju wrote:
> In order for datapath to be restored to normal functionality after resume
> we disable all wakeup events. Additionally we clear all W1C status bits by
> writing 1's to them.

Just to make sure i'm understanding this correctly, you are just
clearing that there was been a WoL wakeup. The WoL configuration is
not cleared, so i could suspend the device again and wake it up with
WoL. There is no need for me to use ethtool, the WoL configuration is
preserved.

	Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ