linux/drivers/net/wireless, branch v2.6.30.4

netdev: restore MAC address set and validate operations

2009-07-30T21:40:30Z

commit 240c102d9c54fee7fdc87a4ef2fabc7eb539e00a upstream. alloc_etherdev() used to install default implementations of these operations, but they must now be explicitly installed in struct net_device_ops. Signed-off-by: Ben Hutchings Signed-off-by: David S. Miller Signed-off-by: Greg Kroah-Hartman

ath5k: avoid PCI FATAL interrupts by restoring RETRY_TIMEOUT disabling

2009-07-02T23:50:28Z

commit 8451d22dad40a66416b8d9c0952efa09ec5398c5 upstream. This reverts 'ath5k: remove dummy PCI "retry timeout" fix' on the same theory as in 'ath9k: Fix PCI FATAL interrupts by restoring RETRY_TIMEOUT disabling'. Reported-by: Bob Copeland Signed-off-by: John W. Linville Signed-off-by: Greg Kroah-Hartman

ath9k: Fix PCI FATAL interrupts by restoring RETRY_TIMEOUT disabling

2009-07-02T23:50:18Z

commit f0214843ba23d9bf6dc6b8ad2c6ee27b60f0322e upstream. An earlier commit, 'ath9k: remove dummy PCI "retry timeout" fix', removed code that was documented to disable RETRY_TIMEOUT register (PCI reg 0x41) since it was claimed to be a no-op. However, it turns out that there are some combinations of hosts and ath9k-supported cards for which this is not a no-op (reg 0x41 has value 0x80, not 0) and this code (or something similar) is needed. In such cases, the driver may be next to unusable due to very frequent PCI FATAL interrupts from the card. Reverting the earlier commit, i.e., restoring the RETRY_TIMEOUT disabling, seems to resolve the issue. Since the removal of this code was not based on any known issue and was purely a cleanup change, the safest option here is to just revert that commit. Should there be desire to clean this up in the future, the change will need to be tested with a more complete coverage of cards and host systems. http://bugzilla.kernel.org/show_bug.cgi?id=13483 Signed-off-by: Jouni Malinen Signed-off-by: John W. Linville Signed-off-by: Greg Kroah-Hartman

ath9k: Initialize ANI timers

2009-07-02T23:50:14Z

commit 415f738ecf41b427921b503ecfd427e26f89dc23 upstream. The various ANI timers have to be initialized properly when starting the calibration timer. Signed-off-by: Sujith Signed-off-by: John W. Linville Signed-off-by: Greg Kroah-Hartman

ath9k: Fix memleak on TX DMA failure

2009-07-02T23:50:13Z

commit 675902ef822c114c0dac17ed10eed43eb8f5c9ec upstream. The driver-specific region has to be freed in case of a DMA mapping failure. Signed-off-by: Sujith Signed-off-by: John W. Linville Signed-off-by: Greg Kroah-Hartman

ath9k: Fix bug in scan termination

2009-07-02T23:50:12Z

commit 9c07a7777f44c7e39accec5ad8c4293d6a9b2a47 upstream. A full HW reset needs to be done on termination of a scan run. Not setting SC_OP_FULL_RESET resulted in doing a fast channel change. Signed-off-by: Sujith Signed-off-by: John W. Linville Signed-off-by: Greg Kroah-Hartman

ath9k: Fix bug in checking HT flag

2009-07-02T23:50:12Z

commit db2f63f60a087ed29ae04310c1076c61f77a5d20 upstream. The operating HT mode is stored in chanmode and not channelFlags. Signed-off-by: Sujith Signed-off-by: John W. Linville Signed-off-by: Greg Kroah-Hartman

ath9k: Fix bug in determining calibration support

2009-07-02T23:50:12Z

commit a451aa66dcb14efcb7addf1d8edcac8df76a97b6 upstream. ADC gain calibration has to be done for all non 2GHZ-HT20 channels. Regression from "ath9k: use ieee80211_conf on ath9k_hw_iscal_supported()" Signed-off-by: Sujith Signed-off-by: John W. Linville Signed-off-by: Greg Kroah-Hartman

ath9k: Fix bug in calibration initialization

2009-07-02T23:50:11Z

commit 04d19ddd254b404703151ab25aa5041e50ff40f7 upstream. This patch fixes a bug in ath9k_hw_init_cal() where the wrong calibration was being done for non-AR9285 chipsets. Also add a few helpful comments. Signed-off-by: Sujith Signed-off-by: John W. Linville Signed-off-by: Greg Kroah-Hartman

ath9k: Fix bug when using a card with a busted EEPROM

2009-07-02T23:50:11Z

backport of commit 85efc86eb7c6cbb1c8ce8d99b10b948be033fbb9 upstream. We fail if your EEPROM is busted but we were never propagated the error back so such users could end up with a cryptic oops message like: IP: [] ath9k_reg_apply_world_flags+0x29/0x130 [ath9k] *pde = 00000000 Oops: 0000 [#1] SMP Modules linked in: ath9k(+) mac80211 cfg80211 Pid: 4284, comm: insmod Not tainted (2.6.29-wl #3) 7660A14 EIP: 0060:[] EFLAGS: 00010286 CPU: 1 EIP is at ath9k_reg_apply_world_flags+0x29/0x130 [ath9k] Fix this by propagating the error and also lets not leave the user in the dark and communicate what's going on. When this happens you will now see this: ath9k 0000:16:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 ath9k: Invalid EEPROM contents Signed-off-by: Luis R. Rodriguez Signed-off-by: John W. Linville Signed-off-by: Greg Kroah-Hartman