From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: Broadcom 43xx first results Date: Mon, 05 Dec 2005 13:46:43 -0500 Message-ID: <43948B13.2090509@pobox.com> References: <20051205190038.04b7b7c1@griffin.suse.cz> <1133806444.4498.35.camel@gimli> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jiri Benc , mbuesch@freenet.de, linux-kernel@vger.kernel.org, bcm43xx-dev@lists.berlios.de, NetDev Return-path: To: netdev@nospam.otaku42.de In-Reply-To: <1133806444.4498.35.camel@gimli> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Michael Renzmann wrote: > Hi. > > On Mon, 2005-12-05 at 19:00 +0100, Jiri Benc wrote: > >>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? > > > Or, in case there is some unknown objection to the mentioned code: use > the 802.11 stack that comes along with MadWifi, which provides things > like virtual interfaces (for multiple SSID support on one physical card) > and WPA support. > > Although I'm a bit biased towards MadWifi, I'd second your suggestion to > make use of the Devicescape code. The benefit of having a fully-blown > 802.11 stack in the kernel that drivers can make use of has been > discussed before, so I won't go into that yet again. Use the stack that's already in the kernel. Encouraging otherwise hinders continued wireless progress under Linux. Jeff