iwn(4) Intel 802.11n series NICs
Overview
The iwn(4) driver supports the Intel 802.11n series wireless NICs.
Hardware List
Make |
Supported Bands |
Streams |
Antennas |
Bluetooth? |
More information |
Tester |
Intel Centrino Wireless-N 100 |
2GHz |
1x1 |
2 |
No |
http://ark.intel.com/products/59478/Intel-Centrino-Wireless-N-100-Single-Band |
|
Intel Centrino Wireless-N 130 |
||||||
Intel Centrino Wireless-N 1000 |
||||||
Intel Centrino Wireless-N 1030 |
||||||
Intel Centrino Wireless-N 2200 |
|
|
|
|
|
Eitan Adler |
Intel Centrino Wireless-N 2230 |
||||||
Intel Wireless WiFi Link 4965 |
2GHz, 5GHz |
2x2 |
2T, 3R |
Unknown |
http://www.intel.com/products/wireless/wireless_n/overview.htm |
|
Intel WiFi Link 5100 |
||||||
Intel WiMAX/WiFi Link 5150 |
||||||
Intel Ultimate N WiFi Link 5300 |
||||||
Intel WiMAX/WiFi Link 5350 |
||||||
Intel Centrino Advanced-N 6200 |
2GHz, 5GHz |
2x2 |
2 |
No |
http://ark.intel.com/products/59470/Intel-Centrino-Advanced-N-6200-Dual-Band |
Adrian Chadd |
Intel Centrino Advanced-N 6205 |
2GHz, 5GHz |
2x2 |
2 |
No |
http://ark.intel.com/products/59471/Intel-Centrino-Advanced-N-6205-Dual-Band |
Adrian Chadd |
Intel Centrino Advanced-N 6230 |
||||||
Intel Centrino Wireless-N + WiMAX 6150 |
||||||
Intel Centrino Advanced-N + WiMAX 6250 |
||||||
Intel Centrino Ultimate-N 6300 |
Known Issues
- Doing a single channel-at-a-time scan is causing issues when scanning some passive channels. Scans of those channels can take up to two minutes. Net80211 doesn't deal well with this kind of failure, but at least things now recover in -HEAD.
- The A-MPDU transmit path occasionally gets the sequence number and transmit ring index out of sync and this causes A-MPDU transmit to stop working reliably. On later chips (eg 6xxx series) the firmware seems to panic when this occurs.
TODO
- Merge in thermal throttling from Linux iwlwifi.
- Extend net80211 to allow all of the scan code to be overridden; that way iwn(4) can do a full band scan in one command without doing individual channel changes and scans. It can do all of the background scanning and traffic handling in firmware.
- Finish merging in work to do a channel change to retune the RF after some PLCP errors.
- Add some way to log commands and command responses to the net80211 alq API, so debugging and diagnostics can be done.
- Look at the RX statistics and see what is worth tracking per-channel for live diagnostics, like channel busy, error rates, etc