summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorNikolay Ledovskikh <nledovskikh@gmail.com>2011-02-18 17:59:53 +0100
committerJohn W. Linville <linville@tuxdriver.com>2011-02-18 22:47:37 +0100
commit28bec7b845e10b68e6ba1ade5de0fc566690fc61 (patch)
tree7d3d65121f726e89a22e20d15c08511bcebc6364 /drivers
parentwireless: rt2x00: rt2800pci.c: add two ids (diff)
downloadlinux-28bec7b845e10b68e6ba1ade5de0fc566690fc61.tar.xz
linux-28bec7b845e10b68e6ba1ade5de0fc566690fc61.zip
ath5k: Correct channel setting for AR2317 chip
Correct channel setting function must be used for AR2317. When I tested ahb patch on bullet2 all seemed to work fine, but it couldn't connect another host (using ibss for example). During an analysis I observed that it's transmitting on another channel. I looked into madwifi code and understood that the problem is in channel setting function. So atheros RF2317 not fully handled in the current ath5k version and must be patched. Signed-off-by: Nikolay Ledovskikh <nledovskikh@gmail.com> Acked-by: Bob Copeland <me@bobcopeland.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/net/wireless/ath/ath5k/phy.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/net/wireless/ath/ath5k/phy.c b/drivers/net/wireless/ath/ath5k/phy.c
index 78c26fdccad1..c44111fc98b7 100644
--- a/drivers/net/wireless/ath/ath5k/phy.c
+++ b/drivers/net/wireless/ath/ath5k/phy.c
@@ -1253,6 +1253,7 @@ static int ath5k_hw_channel(struct ath5k_hw *ah,
case AR5K_RF5111:
ret = ath5k_hw_rf5111_channel(ah, channel);
break;
+ case AR5K_RF2317:
case AR5K_RF2425:
ret = ath5k_hw_rf2425_channel(ah, channel);
break;