From: Dave Jones <davej@redhat.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Jiri Benc <jbenc@suse.cz>, Joseph Jezak <josejx@gentoo.org>,
mbuesch@freenet.de, linux-kernel@vger.kernel.org,
bcm43xx-dev@lists.berlios.de, NetDev <netdev@vger.kernel.org>
Subject: Re: Broadcom 43xx first results
Date: Mon, 5 Dec 2005 14:53:29 -0500 [thread overview]
Message-ID: <20051205195329.GB19964@redhat.com> (raw)
In-Reply-To: <4394902C.8060100@pobox.com>
On Mon, Dec 05, 2005 at 02:08:28PM -0500, Jeff Garzik wrote:
> Jiri Benc wrote:
> >On Mon, 05 Dec 2005 13:38:37 -0500, Joseph Jezak wrote:
> >
> >>We're not writing an entire stack. We're writing a layer that sits in
> >>between the current ieee80211 stack that's already present in the kernel
> >>and drivers that do not have a hardware MAC. Since ieee80211 is already
> >>in use in the kernel today, this seemed like a natural and useful
> >>extension to the existing code. I agree that it's somewhat wasteful to
> >>keep rewriting 802.11 stacks and we considered other options, but it
> >>seemed like a more logical choice to work with what was available and
> >>recommended than to use an external stack.
> >
> >
> >Unfortunately, the only long-term solution is to rewrite completely the
> >current in-kernel ieee80211 code (I would not call it a "stack") or
> >replace it with something another. The current code was written for
> >Intel devices and it doesn't support anything else - so every developer
>
> Patently false.
>
> ieee80211 is used by Intel. Some bits used by HostAP, which also
> duplicates a lot of ieee80211 code. And bcm43xx. And another couple
> drivers found in -mm or out-of-tree.
Orinoco also uses it now no ?
Dave
next prev parent reply other threads:[~2005-12-05 19:54 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 18:50 Broadcom 43xx first results mbuesch
2005-12-04 19:52 ` [Bcm43xx-dev] " Feyd
2005-12-04 19:58 ` Michael Buesch
2005-12-05 5:50 ` Jouni Malinen
2005-12-05 6:05 ` Benjamin Herrenschmidt
2005-12-05 11:08 ` Michael Buesch
2005-12-05 14:19 ` Jouni Malinen
2005-12-05 14:28 ` Michael Buesch
2005-12-05 14:41 ` Jouni Malinen
2005-12-05 18:52 ` Jeff Garzik
2005-12-05 19:20 ` Christoph Hellwig
2005-12-05 18:00 ` Jiri Benc
2005-12-05 18:14 ` Michael Renzmann
2005-12-05 18:24 ` Stephen Hemminger
2005-12-05 18:46 ` Jeff Garzik
2005-12-05 18:49 ` Jiri Benc
2005-12-05 18:54 ` Jeff Garzik
2005-12-05 19:11 ` Jiri Benc
2005-12-30 10:34 ` Rakotomandimby Mihamina
2005-12-06 7:17 ` Michael Renzmann
2005-12-05 18:38 ` Joseph Jezak
2005-12-05 18:38 ` Joseph Jezak
2005-12-05 18:55 ` Jiri Benc
2005-12-05 19:08 ` Jeff Garzik
2005-12-05 19:18 ` Jiri Benc
2005-12-05 19:53 ` Dave Jones [this message]
2005-12-05 20:09 ` Jeff Garzik
2005-12-06 15:10 ` Harald Welte
2005-12-06 19:05 ` Jeff Garzik
2005-12-06 20:53 ` Stephen Hemminger
2005-12-07 7:16 ` Harald Welte
2005-12-06 23:19 ` David S. Miller
2005-12-06 23:45 ` Jeff Garzik
2005-12-07 13:34 ` Michael Buesch
2005-12-08 11:32 ` Jiri Benc
2005-12-08 12:07 ` Jiri Benc
2005-12-08 12:12 ` Arjan van de Ven
2005-12-08 13:03 ` Jiri Benc
2005-12-05 19:10 ` Christoph Hellwig
2005-12-05 19:31 ` Jiri Benc
2005-12-05 19:41 ` Christoph Hellwig
2005-12-05 20:11 ` Jiri Benc
2005-12-06 15:09 ` Pavel Machek
2005-12-06 16:43 ` Ben Greear
2005-12-06 23:25 ` David S. Miller
2005-12-06 19:24 ` Jeff Garzik
2005-12-06 15:04 ` Pavel Machek
2005-12-08 0:00 ` Michael Wu
2005-12-08 1:05 ` Jeff Garzik
2005-12-05 20:23 ` Michael Buesch
2005-12-05 20:23 ` Michael Buesch
2005-12-05 20:42 ` Jiri Benc
2005-12-06 9:26 ` Kyle Moffett
2005-12-06 10:23 ` Luc Saillard
2005-12-05 19:40 ` Pavel Machek
2005-12-05 20:14 ` Michael Buesch
2005-12-05 20:35 ` Pavel Machek
2005-12-05 20:40 ` Arjan van de Ven
2005-12-05 20:40 ` Michael Buesch
-- strict thread matches above, loose matches on Subject: below --
2005-12-06 22:47 Jean Tourrilhes
2005-12-07 7:11 ` Jouni Malinen
2005-12-07 19:16 ` Jean Tourrilhes
2005-12-07 19:47 ` Jouni Malinen
2005-12-07 19:05 ` Jean Tourrilhes
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=20051205195329.GB19964@redhat.com \
--to=davej@redhat.com \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=jbenc@suse.cz \
--cc=jgarzik@pobox.com \
--cc=josejx@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbuesch@freenet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.