From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Williams <dcbw@redhat.com>
Cc: netdev@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Michael Buesch <mb@bu3sch.de>, Jean Tourrilhes <jt@hpl.hp.com>,
Jiri Benc <jbenc@suse.cz>,
"James P. Ketrenos" <ipw2100-admin@linux.intel.com>,
Mohamed Abbas <mabbas@linux.intel.com>,
Ulrich Kunitz <kune@deine-taler.de>,
Daniel Drake <dsd@gentoo.org>
Subject: Re: more nl80211 stuff
Date: Thu, 14 Sep 2006 15:55:46 +0200 [thread overview]
Message-ID: <1158242146.2936.70.camel@ux156> (raw)
In-Reply-To: <1158241289.2634.7.camel@localhost.localdomain>
On Thu, 2006-09-14 at 09:41 -0400, Dan Williams wrote:
> Can you describe a bit more what the scope of each of nl80211 and
> cfg80211 is? Not sure I entirely understand the split and where the
> line is drawn.
Basically, I figured that cfg80211 is the kernel-internal interface and
nl80211 is just the primary userspace interface with WE compatibility
being a second one and possibly partial configurability in configfs
later. All drivers need to care about is cfg80211, hence I made the
split explicit.
johannes
prev parent reply other threads:[~2006-09-14 13:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 10:46 more nl80211 stuff Johannes Berg
2006-09-14 10:49 ` [RFC 1/3] cfg80211/nl80211 core Johannes Berg
2006-09-22 15:48 ` Jiri Benc
2006-09-25 9:05 ` Johannes Berg
2006-10-06 9:51 ` Johannes Berg
2006-09-14 10:50 ` [RFC 2/3] make d80211 use cfg80211 Johannes Berg
2006-09-14 17:53 ` Simon Barber
2006-09-15 6:41 ` Johannes Berg
2006-09-14 10:53 ` [RFC 3/3] cfg80211 thoughts on configuration Johannes Berg
2006-09-20 6:33 ` Thomas Graf
2006-09-20 7:03 ` Johannes Berg
2006-09-20 7:07 ` Thomas Graf
2006-09-14 13:41 ` more nl80211 stuff Dan Williams
2006-09-14 13:55 ` Johannes Berg [this message]
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=1158242146.2936.70.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--cc=dsd@gentoo.org \
--cc=ipw2100-admin@linux.intel.com \
--cc=jbenc@suse.cz \
--cc=jt@hpl.hp.com \
--cc=kune@deine-taler.de \
--cc=linville@tuxdriver.com \
--cc=mabbas@linux.intel.com \
--cc=mb@bu3sch.de \
--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).