From: Kalle Valo <kalle.valo@nokia.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "Helmut Schaa" <hschaa@suse.de>, "Dan Williams" <dcbw@redhat.com>,
linux-wireless@vger.kernel.org,
"Johannes Berg" <johannes@sipsolutions.net>,
"Jouni Malinen" <j@w1.fi>
Subject: Re: [RFC] mac80211: notify the user space about low signal quality
Date: Tue, 16 Sep 2008 11:07:35 +0300 [thread overview]
Message-ID: <87r67kzf7c.fsf@nokia.com> (raw)
In-Reply-To: <43e72e890809151821h5d40e750q10c78f4d20d27c79@mail.gmail.com> (ext Luis R. Rodriguez's message of "Mon\, 15 Sep 2008 18\:21\:17 -0700")
Luis R. Rodriguez <mcgrof@gmail.com> writes:
> On Mon, Sep 15, 2008 at 9:45 AM, Helmut Schaa <hschaa@suse.de> wrote:
>
>> Ok, I'll sum that up. Moving the policy into user space is a good
>> thing if the quality values are comparable. Once mac80211
>> recognices a noticable quality change we could use IWEVQUAL to
>> notify user space about it. Furthermore (if desired) the signal
>> could be extended to not only report a value between 0 and 100 but
>> could also contain flags indicating lost beacons, excessive retries
>> etc.
>
> If you are going to add a new sort of notification can you please use
> nl80211? No need to keep wireless extensions on life support.
>From my point of view WE is not on life support (yet) but instead very
widely used. As an example, I still haven't seen any cfg80211/nl80211
user space tools in debian unstable. (Please correct me if I'm wrong.)
There has been a lot of talk about cfg80211/nl80211 but unfortunately
the migration progress has been very slow.
I definitely want to see this background scan support in Wireless
Extensions as well, otherwise it might prevent the real use of the
feature.
--
Kalle Valo
next prev parent reply other threads:[~2008-09-16 8:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 12:16 More thoughts about roaming Helmut Schaa
2008-09-15 12:29 ` [RFC] Implement basic background scanning Helmut Schaa
2008-09-15 14:32 ` Michael Buesch
2008-09-15 14:40 ` Helmut Schaa
2008-09-15 15:59 ` Johannes Berg
2008-09-15 16:35 ` Helmut Schaa
2008-09-16 8:43 ` Kalle Valo
2008-09-16 9:10 ` Johannes Berg
2008-09-16 9:20 ` Helmut Schaa
2008-09-16 11:06 ` Johannes Berg
2008-09-16 9:15 ` Tomas Winkler
2008-09-15 12:35 ` [RFC] mac80211: notify the user space about low signal quality Helmut Schaa
2008-09-15 14:07 ` Dan Williams
2008-09-15 14:34 ` Helmut Schaa
2008-09-15 15:28 ` Dan Williams
2008-09-15 16:45 ` Helmut Schaa
2008-09-16 1:21 ` Luis R. Rodriguez
2008-09-16 7:41 ` Helmut Schaa
2008-09-16 8:07 ` Kalle Valo [this message]
2008-09-16 8:12 ` Johannes Berg
2008-09-16 8:55 ` Kalle Valo
2008-09-23 18:21 ` John W. Linville
2008-09-16 8:00 ` Kalle Valo
2008-09-16 7:57 ` Kalle Valo
2008-09-15 15:10 ` Holger Schurig
2008-09-15 15:19 ` Dan Williams
2008-09-16 8:25 ` Kalle Valo
2008-09-16 8:50 ` Holger Schurig
2008-09-16 9:25 ` Helmut Schaa
2008-09-16 9:32 ` Helmut Schaa
2008-09-16 10:23 ` Holger Schurig
2008-09-15 15:17 ` Holger Schurig
2008-09-16 7:53 ` Kalle Valo
2008-09-15 12:41 ` [RFC] wpa_supplicant: trigger a scan if signal quality is low Helmut Schaa
2008-09-15 13:59 ` More thoughts about roaming Dan Williams
2008-09-15 14:18 ` Helmut Schaa
2008-09-15 14:45 ` Dan Williams
2008-09-16 7:09 ` Kalle Valo
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=87r67kzf7c.fsf@nokia.com \
--to=kalle.valo@nokia.com \
--cc=dcbw@redhat.com \
--cc=hschaa@suse.de \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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).