All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Michael Wu <flamingice@sourmilk.net>,
	Simon Barber <simon@devicescape.com>,
	David Kimdon <david.kimdon@devicescape.com>,
	netdev@vger.kernel.org, Jiri Benc <jbenc@suse.cz>,
	"John W. Linville" <linville@tuxdriver.com>,
	Jean Tourrilhes <jt@hpl.hp.com>, Hong Liu <hong.liu@intel.com>,
	Jouni Malinen <jkmaline@cc.hut.fi>
Subject: Re: [RFC] [PATCH 0/3] Add Regulatory Domain support to d80211
Date: Thu, 26 Oct 2006 11:33:03 -0400	[thread overview]
Message-ID: <1161876783.2927.37.camel@localhost.localdomain> (raw)
In-Reply-To: <43e72e890610260804q28505f71v6053f8dbbd457ac7@mail.gmail.com>

On Thu, 2006-10-26 at 11:04 -0400, Luis R. Rodriguez wrote:
> On 10/26/06, Dan Williams <dcbw@redhat.com> wrote:
> > While wpa_supplicant is certainly the main client for stuff directly
> > related to setting up a connection, there are quite a few other users of
> > general WE calls to pull information out of the card, or to receive scan
> > events.
> 
> How about we just ditch iwconfig completely and move on to
> wpa_supplicant/wpa_cli as our next userspace application with
> nl80211/cg80211 as our new API for usersapce-->kernel communication?
> As you point out, wpa_supplicant already does a lot for us -- and
> several distributions already rely on it. Some work is required but I
> think its worth it. If we do a complete move from WE to nl80211 it
> would be transparent to the users too.

The one blocker I can think of here is startup scripts on various
distributions.  Most of those are shell, and they usually rely on
iwconfig quite heavily.  Getting those converted to wpa_supplicant
wouldn't be a trivial amount of work, but it wouldn't be a ton either.

Dan


  reply	other threads:[~2006-10-26 15:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-23 22:41 [RFC] [PATCH 0/3] Add Regulatory Domain support to d80211 Luis R. Rodriguez
2006-10-23 23:32 ` Johannes Berg
2006-10-24  5:33   ` Luis R. Rodriguez
2006-10-24 12:03     ` John W. Linville
2006-10-24 17:41       ` Luis R. Rodriguez
2006-10-25  8:24         ` Jiri Benc
2006-10-25 16:18           ` Luis R. Rodriguez
2006-10-24  8:25 ` Johannes Berg
2006-10-24 17:31   ` Luis R. Rodriguez
2006-10-24 14:02 ` David Kimdon
2006-10-24 17:47   ` Luis R. Rodriguez
2006-10-24 20:03   ` Simon Barber
2006-10-24 22:03     ` Luis R. Rodriguez
2006-10-24 22:52       ` Michael Wu
2006-10-25 17:43         ` Luis R. Rodriguez
2006-10-25 22:00           ` Johannes Berg
2006-10-26 14:35             ` Dan Williams
2006-10-26 14:43               ` Johannes Berg
2006-10-26 15:04               ` Luis R. Rodriguez
2006-10-26 15:33                 ` Dan Williams [this message]
2006-10-26 21:41                   ` Simon Barber
2006-10-26 21:47                     ` Johannes Berg
2006-10-26 21:48                   ` Johannes Berg
2006-10-24 22:56       ` Simon Barber
2006-10-25  5:03         ` Dan Williams

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=1161876783.2927.37.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=david.kimdon@devicescape.com \
    --cc=flamingice@sourmilk.net \
    --cc=hong.liu@intel.com \
    --cc=jbenc@suse.cz \
    --cc=jkmaline@cc.hut.fi \
    --cc=johannes@sipsolutions.net \
    --cc=jt@hpl.hp.com \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=simon@devicescape.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 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.