From: Alexander Sack <asac@ubuntu.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
"hostap@lists.shmoo.com" <hostap@lists.shmoo.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
networkmanager-list <networkmanager-list@gnome.org>
Subject: Re: Incorrect signal levels reported using wpa_supplicant's driver_nl80211
Date: Mon, 9 Nov 2009 13:50:16 +0100 [thread overview]
Message-ID: <20091109125016.GK1579@jwsdot.com> (raw)
In-Reply-To: <1257190833.1027.4.camel@localhost.localdomain>
On Mon, Nov 02, 2009 at 11:40:33AM -0800, Dan Williams wrote:
> On Sat, 2009-10-31 at 03:50 +0200, Maxim Levitsky wrote:
> > Sorry for cross-posting, but this issue really spans all three systems.
> >
> > I anylized why I get 100% quality on all access points except currently
> > connected, when I used driver_nl80211 of wpa_supplcant.
> >
> > First, when NetworkManager plans to switch to this driver?
>
> Soon. We've got some patches for this, but we'll also need tons of
> testing. The WEXT stuff is pretty baked while nl80211 is still under
> some flux. But of course the only way we bake nl80211 is by switching
> to it...
iirc, we currently we hardcode wext in NM code. How about adding a keyfile
config that users could use to switch to nl80211 until we feel confident
that it's good enough for everyone?
- Alexander
next prev parent reply other threads:[~2009-11-09 12:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 1:50 Incorrect signal levels reported using wpa_supplicant's driver_nl80211 Maxim Levitsky
2009-11-02 19:40 ` Dan Williams
2009-11-02 23:07 ` Maxim Levitsky
2009-11-03 0:53 ` Dan Williams
2009-11-03 8:06 ` Johannes Berg
2009-11-09 12:50 ` Alexander Sack [this message]
2009-11-09 12:54 ` Johannes Berg
2009-11-09 13:09 ` Marcel Holtmann
2009-11-10 6:27 ` Dan Williams
2009-11-10 8:41 ` Marcel Holtmann
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=20091109125016.GK1579@jwsdot.com \
--to=asac@ubuntu.com \
--cc=dcbw@redhat.com \
--cc=hostap@lists.shmoo.com \
--cc=linux-wireless@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=networkmanager-list@gnome.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.