Driver ipw2200 needs updating

Rated 3.89/5 based on 859 customer reviews

(thanks to Stephen Hemminger) * Fixed TCP session freezing problem (thanks to Yi Zhu) * Added support for non-broadcasting ESSIDs (thanks to Andreas Oberritter) Thanks, James You can pull the latest snapshot from Or you can resync your tree with bk://[email protected]/ipw-2.6 Anyway, here are the changes in 0.54... * Test fix for spurious IRQs during firmware intialization. i thought there were more WE-18 IOCTLs =:-) Anyway, IOCTLs don't cost money, what really matters is that when you choose the private IOCTL interface for WPA you should stick to it until WE-18 arrives.

* Fixed payload_size bug in fragmentation code (thanks to Yi Zhu) * Removed "IRQ ignored" message. nav=Dax Kelson Guru Labs One hassle with ioctl's is 32/64 bit compatibility. The translation has to be done before it gets down to the device, which makes it impossible for SIOCDEVPRIVATE ioctl's. We don't want people having troubles with the interface changing over time and having to keep track of which wpa_supplicant versions work with which ipw2100 driver version.

At some point in the near future we will rename the ipw2200 project to something more appropriate to identify it as supporting both the 22 adapters.

Thanks, James Latest snapshot for the 2200 is here: As with the ipw2100, you can get the latest bits from Bit Keeper at bk://[email protected]/ipw-2.6 I think I caught all of the fixes/patches.

* Moved probe / beacon handling into ieee module (shared with ipw2100) * Changed to use netdev_priv consistently (thanks to Stephen Hemminger) * Fix the initialization code (thanks to Stephen Hemminger): - memset is unnecessary since alloc_etherdev does it already SET_NETDEV_DEV so that /sys/class/net/eth0/device symlink is created - don't set name to "eth%d" already done by alloc_etherdev - don't mask register_netdev error codes * Misc.

code cleanup (thanks to Stephen Hemminger): * get rid of left over cruft in ipw2200 priv stuff that is set but never used * debug/channel should be local variables (global namespace conflicts possible).

We are in the process of cleaning up the driver for submittal to netdev for eventual inclusion into the kernel.

Also removes unused long_preamble variable (thanks to Lubomir Gelo) * Resynced ieee80211 with ipw2200 (moved scan and probe logic from ipw module into ieee80211 module) Thanks, James Did i miss something? - Only one set of IOCTL handlers and respective auxiliary functions are needed in the driver (no need to create different IOCTL handlers for different WPA IOCTL sets).

Not a problem if all elements of the ioctl are just u32, u16, u64, etc. The support by folks in the community has been terrific -- the drivers wouldn't be anywhere near as feature rich and stable as they are today if not for the contributions of everyone.

which makes it impossible for SIOCDEVPRIVATE ioctl's. Are the problems related to the data passed to the IOCTL? The ipw2100 project (802.11b) has progressed very well.

To that end we're working to try and get it ready for submittal along with the ipw2100 project. The ipw2100 and ipw2200 projects currently share the 802.11 frame handling stack for Tx/Rx and some management frame processing.

That code has been pulled into its own module suite (ieee80211), based on work from the Host AP project.

Leave a Reply