netdev
[Top] [All Lists]

Re: [RFC] acx100 inclusion in mainline; generic 802.11 stack

To: Vladimir Kondratiev <vkondra@xxxxxxx>
Subject: Re: [RFC] acx100 inclusion in mainline; generic 802.11 stack
From: mcgrof@xxxxxxxxxxxxxxxxxxxx (Luis R. Rodriguez)
Date: Tue, 31 Aug 2004 17:37:19 -0400
Cc: netdev@xxxxxxxxxxx, Jeff Garzik <jgarzik@xxxxxxxxx>, Denis Vlasenko <vda@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>, Jean Tourrilhes <jt@xxxxxxxxxxxxxxxxxx>, Jouni Malinen <jkmaline@xxxxxxxxx>, acx100-devel@xxxxxxxxxxxxxxxxxxxxx, prism54-devel@xxxxxxxxxxx, davem@xxxxxxxxxx
In-reply-to: <200408312214.44701.vkondra@mail.ru>
Mail-followup-to: Vladimir Kondratiev <vkondra@xxxxxxx>, netdev@xxxxxxxxxxx, Jeff Garzik <jgarzik@xxxxxxxxx>, Denis Vlasenko <vda@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>, Jean Tourrilhes <jt@xxxxxxxxxxxxxxxxxx>, Jouni Malinen <jkmaline@xxxxxxxxx>, acx100-devel@xxxxxxxxxxxxxxxxxxxxx, prism54-devel@xxxxxxxxxxx, davem@xxxxxxxxxx
Organization: Rutgers University Student Linux Users Group
References: <200408312111.02438.vda@port.imtp.ilyichevsk.odessa.ua> <4134C1A7.50600@pobox.com> <200408312214.44701.vkondra@mail.ru>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.28i
On Tue, Aug 31, 2004 at 10:14:38PM +0300, Vladimir Kondratiev wrote:
> On Tuesday 31 August 2004 21:21, Jeff Garzik wrote:
> JG> Denis Vlasenko wrote:
> JG> > I think 'senior' network guys are in position to decide upon which
> JG> > of currently available 802.11 stacks we should continue to work.
> JG> > (Atheros has one, said to be derived from BSD, is there any others?)
> JG>
> JG>
> JG> Already have.  Start with the code in wireless-2.6 -- HostAP -- and use
> JG> DaveM's 802.11 stack template as a model for actually integrating 802.11
> JG> very tightly with the rest of the net stack.
> JG>
> JG>
>  http://www.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.6/davem-p8
> 0211.tar.bz2 JG>
> JG>  Jeff
> 
> This stack raises many questions.
> 
> The very idea to implement generic softmac is pretty good.
> 
> So, first questions:
> 
> - it defines structures that was present in Jean's wireless extensions. So, 
> will it replace Jean's wireless extensions, merge with it, or some other 
> relationship? Partually, I don't like to see definitions for .11 header and 
> field constants in 2 includes.
> 
> - QoS stuff is not defined. I suppose recent cards will all support WME 
> and/or 
> TGe. It is easy to add "QoS control" field to header and new frame types, but 
> it is harder to formally define how PHY should handle it. And, TGe is big 
> story on itself, with all its HCCA, block ack, etc. I also think that QoS, as 
> it is defined in TGe, required driver to have several tx queues and 
> start/stop them separately. Is anyone working on it? I'll be glad to join.
> 
> - Security is not up-to date either. We need .1x, EAS, TKIP etc. This need to 
> be done for modern cards to use this infrastructure.

This is handled by hostap wpa_supplicant now, which is going to be part
of WE18. The question I think is whether somoene plans on re-doing it on
wireless-2.6, since as you mentioned it seems WE are being redone on
davem's patch.

        Luis

-- 
GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84  A34A 6ADD 4937 E20A 525E

<Prev in Thread] Current Thread [Next in Thread>