From: "Jouni Malinen" <jkm@devicescape.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Jiri Benc <jbenc@suse.cz>,
"John W. Linville" <linville@tuxdriver.com>,
netdev@vger.kernel.org, jkmaline@cc.hut.fi
Subject: Re: [PATCH wireless-dev] d80211: Add support for user space clientMLME
Date: Wed, 10 May 2006 10:17:49 -0700 [thread overview]
Message-ID: <20060510171749.GH23571@instant802.com> (raw)
In-Reply-To: <1146745613.1137.28.camel@localhost>
On Thu, May 04, 2006 at 02:26:53PM +0200, Johannes Berg wrote:
> On Wed, 2006-05-03 at 09:44 -0700, Jouni Malinen wrote:
> > But there is.. I committed changes to the wpa_supplicant devel branch
> > for this yesterday. It seems to work fine with net/d80211 and bcm43xx
> > with this small patch to d80211 to allow the functionality to be moved
> > into user space.
>
> Cool, do you have a list of things that we need to support for it to
> work on a 'softmac' based driver (iow removing softmac in favour of
> this)?
This is still somewhat open, but at minimum, there needs to be a
mechanism for receiving and sending management frames from user space.
d80211 uses a "management netdev" for this currently (the same one that
was used before with hostapd for AP mode). In addition to that,
wpa_supplicant expect to be able to read list of support channels and TX
rates (get_hw_feature_data handler in driver wrapper) and to be able to
add and remove STA entries (e.g., for TX rate control and association
status validation in kernel code).
Currently, scanning is done simply by setting the channel with
SIOCSIWFREQ and listening for management frames. However, the goal is to
provide simple atomic operations that user space programs can request
the kernel code to do. This would cover not only scanning, but also some
other needs like IEEE 802.11k radio measurements. These operations could
be something like "stop transmit, move to channel 5, report received
management frames, record noise level, do this for 5 ms, return to
operational channel, enable transmit".
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2006-05-10 17:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 21:18 [PATCH wireless-dev] d80211: Add support for user space client MLME Jouni Malinen
2006-05-03 16:28 ` Jiri Benc
2006-05-03 16:44 ` Jouni Malinen
2006-05-03 18:10 ` Jiri Benc
2006-05-03 18:35 ` Jouni Malinen
2006-05-04 9:00 ` Jiri Benc
2006-05-04 16:44 ` Jouni Malinen
2006-05-05 10:13 ` Johannes Berg
2006-05-05 13:17 ` [PATCH] d80211: switching management interface on/off Jiri Benc
2006-05-04 12:26 ` [PATCH wireless-dev] d80211: Add support for user space client MLME Johannes Berg
2006-05-10 17:17 ` Jouni Malinen [this message]
2006-05-11 11:41 ` [PATCH wireless-dev] d80211: Add support for user space clientMLME Johannes Berg
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=20060510171749.GH23571@instant802.com \
--to=jkm@devicescape.com \
--cc=jbenc@suse.cz \
--cc=jkmaline@cc.hut.fi \
--cc=johannes@sipsolutions.net \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.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).