On Wednesday 08 September 2004 22:51, Vladimir Kondratiev wrote:
> you missed one important point. Besides data packets, that every driver now
> convert .11<->.3 using almost the same code, there is whole story of
> management. Many modern cards are "softmac" and do all management on host.
> I see no point for every driver to implement its own scanning and
> association. It is simply waste of resources.
This is exactly what I meant. We need generic 802.11 idioc^W management
handling. And maybe also tx rate control, ACK/retries for "completely-softmac"
cards like Atheros.
Full spectrum of possible fullmac......softmac designs are not trivial
> To make step forward, I suggest the following:
> 1. Dave's code is at least year old. someone need to start maintain it,
> starting with update for current kernel infrastructure. Get it compile and
> load for 2.6.9, for example.
/me runs away and hides
> 2. To debug stack, you don't need real driver. I can write dummy .11 driver
> that will silently discard all Tx, and will provide some way for user level
> tool to simulate Rx (ioctl, netlink, does not really matter). For logic, it
> is sufficient. Later, when it will come to timing, performance etc, it will
> be easy to strip some real driver.