Hi rt2x00-devel & netdev lists, First I would like to wish everybody a happy new year!
Secondly I would like to make the announcement that the rt2x00 project has decided to switch ieee80211 stack used in the rt2x00-beta series. Up to Beta3 we have used the IPW-stack which was merged into the kernel last year. Unfortunately this stack has not been completely suitable for the rt2x00 needs. It might be usefull for Wireless drivers with Firmware, but for non-firmware drivers, there are several important features lacking. While we have attempted to resolve several bugs within the IPW-stack, we couldn't develop the required features and integrate them into the stack mostly due to lack of ieee80211 knowledge on our side. Immediately after the rt2x00-beta3 release, all development has been focussed on making the rt2x00 drivers use the ieee80211 stack from DeviceScape. This stack seems to contain all features rt2x00 needs, and the rt2x00 design apparantely fits nicely into the DeviceScape stack API, making the switch relatively easy. As previously with the IPW stack, during development of rt2x00 we will also try to help in the development and bugfixing of the DeviceScape stack. I don't know if there is a list of known issues with the stack, but apparently the 80211.ko module doesn't load on a 64bit machine. It fails with the skb->cb size check, because the ieee80211_tx_packet_data structure contains a pointer and unsigned long, which makes the structure 8 bytes larger to 48 bytes on a 64bit machine. The downside of this switch is however is offcourse the kernel integration. Only the IPW stack is present in the kernel, and I am so far unaware of any news about the possibility of the DeviceScape stack being integrated. IvD http://rt2x00.serialmonkey.com
pgpwvaQleBg7V.pgp
Description: PGP signature
