From: Dan Williams <dcbw@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Michael Buesch <mb@bu3sch.de>,
"John W. Linville" <linville@tuxdriver.com>,
Jiri Benc <jbenc@suse.cz>,
netdev@vger.kernel.org
Subject: Re: d80211 merge plans
Date: Wed, 09 Aug 2006 10:37:55 -0400 [thread overview]
Message-ID: <1155134276.3615.16.camel@localhost.localdomain> (raw)
In-Reply-To: <44D9754B.3060909@garzik.org>
On Wed, 2006-08-09 at 01:40 -0400, Jeff Garzik wrote:
> Michael Buesch wrote:
> > To heavily reduce maintainance burden I would like to see d80211
> > going mainline as soon as possible, so that we can feature-freeze
> > the softmac port of bcm43xx and reduce maintainance to next to zero
> > there. So if people want freaky features, we simply point them
> > to the d80211 port, which would coexist in mainline.
> >
> > d80211 in mainline would clearly marked as experimental, for sure.
> > Notes must be added for possibly breaking usermode interfaces.
>
>
> Does it have active maintainers?
>
> The DeviceScape people seem to have disappeared for months, except for a
> rare appearance recently by Jouni.
>
> Did anyone ever come up with a list of why d80211 is superior?
For one, it's got a _much_ more flexible device model than the current
hostap/ipw-based stack, more like the net80211 stack for
Atheros/madwifi. I think that's one of the main benefits. i.e., you
can have the d80211 cards be any combination of [AP | client | wds? ] at
any given time. Think of a repeater node, which is both an AP and
client at the same time, all with one card. That's one of the things a
lot of people like about net80211.
Secondly, DS is also working hard on moving a lot of the higher-level
processing to user space. Management frames and other more complex
operations will eventually be pushed up to a fused wpa_supplicant
+hostapd running in user space, which should (a) reduce the amount of
kernel driver code, (b) increase flexibility of configuration, and (c)
make any kernel API/ABI/etc much smaller since you don't have to push so
much configuration down into the kernel itself.
That's a start (please correct me if I'm wrong on any of this).
Dan
> What are the remaining d80211 issues?
>
> Jeff
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-08-09 14:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 5:03 d80211 merge plans Michael Buesch
2006-08-09 5:40 ` Jeff Garzik
2006-08-09 14:37 ` Dan Williams [this message]
2006-08-09 20:47 ` Jouni Malinen
2006-08-09 5:48 ` David Miller
2006-08-09 8:19 ` Ivo Van Doorn
2006-08-09 20:09 ` Mohamed Abbas
2006-08-10 6:11 ` Jeff Garzik
2006-08-09 9:16 ` Christoph Hellwig
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=1155134276.3615.16.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=jbenc@suse.cz \
--cc=jeff@garzik.org \
--cc=linville@tuxdriver.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).