From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Williams <dcbw@redhat.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
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>
Subject: Re: [RFC] [PATCH 0/3] Add Regulatory Domain support to d80211
Date: Thu, 26 Oct 2006 16:43:35 +0200 [thread overview]
Message-ID: <1161873815.2866.39.camel@ux156> (raw)
In-Reply-To: <1161873333.2927.9.camel@localhost.localdomain>
On Thu, 2006-10-26 at 10:35 -0400, Dan Williams wrote:
> > - I'd like to see a header cleanup, it's necessary. Part of the problem
> > here is all the sub-ioctl WE foo. Clean that up by moving them into
> > cfg80211 as required, there's basically one user, wpa_supplicant (and
> > maybe hostapd), screw the others if there are any
Oh, right, by sub-ioctl I was referring to the mess of the private
ioctls d80211 has for WE, including sub-items again.
> 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.
Of course.
> So if you want maximum compatibility for a limited amount of
> work, you can probably consider wpa_supplicant the only client of
>
> (s = set, g = get)
>
> 1) [s|g] ENCODEEXT
> 2) [s|g] AUTH
> 3) [s|g] MLME
> 4) [s] RATE
> 5) [s] FREQ
> 6) [s] SENS
> 7) [s] AP
> 8) [s|g] RTS
> 9) [s|g] FRAG
> 10)[s|g] GENIE
> 11)[s|g] PMKSA
Sounds about right to me. I did actually intend to keep these intact but
drop the private ones with the 10xx sub-numbers.
> 4) [s|g] POWER (power management does this, not wpa_supplicant)
Does it work for any card?
johannes
next prev parent reply other threads:[~2006-10-26 14:42 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 [this message]
2006-10-26 15:04 ` Luis R. Rodriguez
2006-10-26 15:33 ` Dan Williams
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=1161873815.2866.39.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=david.kimdon@devicescape.com \
--cc=dcbw@redhat.com \
--cc=flamingice@sourmilk.net \
--cc=hong.liu@intel.com \
--cc=jbenc@suse.cz \
--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 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).