Am Mittwoch 21 Juni 2006 17:08 schrieb Luis R. Rodriguez:

> Since d80211 is already being patched for sysfs how about we use sysfs
> (and kobjects) to maintain the state at suspend() and resume(). This
> would allow userspace tools like supplicant running in the background
> to pick up from sysfs where it left off and for our drivers to save
> where we left off.

Forgive me that I'm so insistant on this question, but this is important: What 
state that goes beyond the data settable with wireless ioctls/iwconfig (that 
is kept anyway) needs to be saved by the stack? Last association info is 
worthless, the assocation can be restored using the ESSID/BSSID/channel set 
with iwconfig or by wpa_supplicant. Important is that userspace is notified 
about the connection loss. Is there _any_ other information not recreatable 
from iwconfig settings that needs to be kept?

Stefan
-
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

Reply via email to