Message-ID: <4394892D.2090100@gentoo.org>
Date: Mon, 05 Dec 2005 13:38:37 -0500
From: Joseph Jezak <josejx@gentoo.org>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051104)
MIME-Version: 1.0
To: Jiri Benc <jbenc@suse.cz>
CC: mbuesch@freenet.de, linux-kernel@vger.kernel.org,
       bcm43xx-dev@lists.berlios.de, NetDev <netdev@vger.kernel.org>
Subject: Re: Broadcom 43xx first results
References: <E1Eiyw4-0003Ab-FW@www1.emo.freenet-rz.de> <20051205190038.04b7b7c1@griffin.suse.cz>
In-Reply-To: <20051205190038.04b7b7c1@griffin.suse.cz>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1324
Lines: 25

 > Why yet another attempt to write 802.11 stack? Sure, the one currently
 > in the kernel is unusable and everybody knows about it. But why not to
 > improve code opensourced by Devicescape some time ago instead of
 > inventing the wheel again and again? Yes, I know that code is not
 > perfect and needs a lot of work, but it is the best piece of code we
 > have available now. And it _does_ support WPA and such - in fact, it
 > is nearly complete.
 >
 > Please take a look at http://kernel.org/pub/linux/kernel/people/jbenc/

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.

-Joe
-
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/