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

[Vladimir Kondratiev <vkondra@mail.ru>]

[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]

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.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]