From: Stefan Rompf <stefan@loplof.de>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "Michael Buesch" <mb@bu3sch.de>, "Jiri Benc" <jbenc@suse.cz>,
"John W. Linville" <linville@tuxdriver.com>,
netdev@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: Suspending 802.11 drivers
Date: Thu, 22 Jun 2006 00:07:03 +0200 [thread overview]
Message-ID: <200606220007.07467.stefan@loplof.de> (raw)
In-Reply-To: <43e72e890606210808n187771e6k2f58789cf1fcf680@mail.gmail.com>
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
next prev parent reply other threads:[~2006-06-21 22:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 19:58 Suspending 802.11 drivers Michael Buesch
2006-06-15 20:14 ` Ivo van Doorn
[not found] ` <200606152213.01631.florian@alphacore.net>
2006-06-15 20:42 ` Michael Buesch
2006-06-16 18:36 ` Stefan Rompf
2006-06-21 9:42 ` Stefan Rompf
2006-06-21 15:08 ` Luis R. Rodriguez
2006-06-21 20:41 ` Michael Buesch
2006-06-22 5:15 ` Luis R. Rodriguez
2006-06-21 22:07 ` Stefan Rompf [this message]
2006-06-22 10:56 ` Luis R. Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200606220007.07467.stefan@loplof.de \
--to=stefan@loplof.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=jbenc@suse.cz \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=mcgrof@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).