Messages in this thread | | | Date | Mon, 05 Dec 2005 15:09:19 -0500 | From | Jeff Garzik <> | Subject | Re: Broadcom 43xx first results |
| |
Dave Jones wrote: > 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 ?
Just the headers, really.
Jeff
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |