From: Johannes Berg <johannes@sipsolutions.net>
To: "Bar, Eitan" <eitanb@ti.com>
Cc: netdev@vger.kernel.org
Subject: Re: 80211 questions
Date: Wed, 18 Oct 2006 15:29:38 +0200 [thread overview]
Message-ID: <1161178178.5575.24.camel@ux156> (raw)
In-Reply-To: <19EFC4D481EBF849B14F91557CA737B54A6838@dile02.ent.ti.com>
Hi,
> I'm working on adding WE (wireless extensions) support to a WLAN
> driver, and have recently bumped into references of nl80211, cfg80211
> and d80211.
>
> My questions:
> - Can someone please shortly describe each term?
d80211: wireless stack slated to replace the current ieee80211 subsystem
in the kernel, includes very advanced functionality and can drives
softmac chipsets like bcm43xx.
cfg80211: my proposal for the in-kernel wireless configuration interface
replacing WE
nl80211: tightly tied to cfg80211, this exports the cfg80211 interface
over netlink to userspace
There's also a compat interface so drivers can use cfg80211 but
userspace can continue to use WE.
> - Other than reading the source code and searching in news-groups, is
> there any serious source of information regarding any of the above?
not really, sorry. What specifically do you need? Also, what driver are
you adding support for? Could it make sense to make said driver use
d80211, or is it for a fullmac chipset?
> p.s: while I'm at it -> any good documentation on WE itself other than
> wireless.20.h ?
None as far as I know. Jean recommends reading the userspace tools
source code (which from my POV shows just /how/ broken WE is).
johannes
next prev parent reply other threads:[~2006-10-18 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 13:09 80211 questions Bar, Eitan
2006-10-18 13:29 ` Johannes Berg [this message]
2006-10-18 13:45 ` Bar, Eitan
2006-10-18 13:50 ` Johannes Berg
2006-10-18 14:18 ` 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=1161178178.5575.24.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=eitanb@ti.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).