On 6/23/06, John W. Linville <[EMAIL PROTECTED]> wrote:
On Fri, Jun 23, 2006 at 07:50:47AM -0400, Dan Williams wrote:
> Our effort is probably better spent elsewhere, especially since many
> popular userspace tools already handle resume for us just fine. More
> useful to have drivers just come back from resume in an initialized
> state similar to system boot.
I think Dan makes a lot of sense here. Does anyone disagree?
How would we handle resume() when using WPA, for example? Dan are you
suggesting we just bring up the driver clean and expect userspace to
have handled recovery from anything we were doing? This is important.
Or should we just expect the driver to re-set all settings again and
expect wpa_supplicant to pick up well where it left off? If sysfs will
get cleared after resume then there is no point in using it, but if
its stateful after suspend then this is where I suspected
wpa_supplicant could make use of sysfs. Perhaps there is a better way
-- what I suggested was just an idea while we discussed resume/suspend
in another thread. The reason I started a new thread was I figured
configfs/sysfs could be used for other things as well.
Luis
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
