linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Alexander Sack <asac@ubuntu.com>,
	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, 09 Nov 2009 22:27:48 -0800	[thread overview]
Message-ID: <1257834468.15493.31.camel@localhost.localdomain> (raw)
In-Reply-To: <1257772174.3024.11.camel@violet>

On Mon, 2009-11-09 at 14:09 +0100, Marcel Holtmann wrote:
> Hi Johannes,
> 
> > > > 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?
> > 
> > commit d27df100b587dd95f3256a8baf9db0c5d4380089 in wpa_supplicant allows
> > you to do that by editing the service file.
> 
> that is funny, when I asked for a global command line switch for
> choosing a different driver, the argument was that the application
> adding the interface is suppose to do it by itself. Now we can do it in
> the service file. Never the less ConnMan got its own switch to choose
> which driver will be used. Does help a lot in testing and is way easier
> since you don't have to restart wpa_supplicant all the time.

In reality, NM upstream will just switch over one day and distros that
use shitty and/or proprietary drivers will need to either (a) fix them,
or (b) patch NM to use wext locally.  That's how progress gets made.

Dan



  reply	other threads:[~2009-11-10  6:28 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
2009-11-09 12:54     ` Johannes Berg
2009-11-09 13:09       ` Marcel Holtmann
2009-11-10  6:27         ` Dan Williams [this message]
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=1257834468.15493.31.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=asac@ubuntu.com \
    --cc=hostap@lists.shmoo.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.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 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).