On Tue, Dec 06, 2005 at 04:26:50AM -0500, Kyle Moffett wrote: > On Dec 05, 2005, at 15:42, Jiri Benc wrote: > >On Mon, 5 Dec 2005 21:23:42 +0100, Michael Buesch wrote: > >>This is __not__ "yet another stack". It is an _extension_. It is > >>all about management frames, which the in-kernel code does not > >>manage. > > > >But this code should be part of the stack, as nearly every driver > >needs it. > > WRONG. More than half the currently Linux-compatible wireless cards > handle the wireless management packets in hardware, such that they're > little more complicated than a basic ethernet device with a channel, > an ESSID, and a list of MACs/APs. > I do not want to enter in this flamewar, but the current driver i'm working on (marvell libertas chipset) need management frames in software. But to reduce cost, i think that lower chipset try to put the most in the host and not in the chipset. Marvell build the chipset around a ARM cpu so i think one day i can do it in hardware but for now i need to choose a ieee802.11 stack. I've began to used the in kernel solution with my own functions to send and received this frame. But i hope we will find a technical solution that please everyone. I'll try to see if the softmac layer written for broadcom driver can be used for my project.
Luc - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
