On 6/21/06, Stefan Rompf <[EMAIL PROTECTED]> wrote:
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
Stefan, this is an excellent and valid question. Let me elaborate --
Its exactly those settings you mention I'm suggesting get saved onto
sysfs by the driver and later get picked up by userspace. There are,
however, other settings which could get saved when suspending too
though, settings for example, which otherwise would get set by current
private wireless ioctls. There are too many here to describe really,
each device has their own set of of private attributes.
More on this in another e-mail I'm about to send to netdev.
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
