| commit | 240606b385bb9d0a5c4dec19dfd364289bf478ab | |
| author | Rajkumar Manoharan <rmanohar@qca.qualcomm.com> | |
| Sat, 10 Dec 2011 13:29:43 +0000 (10 18:59 +0530) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Fri, 6 Jan 2012 22:17:14 +0000 (6 14:17 -0800) | ||
| tree | 9794d88d6b29ab5c3ad57d7d1e96f16e170aafab | treesnapshot (tar.gz zip) |
| parent | 192b2a0d9c24c2906af52aa69c7c386b9c505a82 | commitdiff |
ath9k: fix max phy rate at rate control init
commit 10636bc2d60942254bda149827b922c41f4cb4af upstream.
The stations always chooses 1Mbps for all trasmitting frames,
whenever the AP is configured to lock the supported rates.
As the max phy rate is always set with the 4th from highest phy rate,
this assumption might be wrong if we have less than that. Fix that.
Cc: Paul Stewart <pstew@google.com>
Reported-by: Ajay Gummalla <agummalla@google.com>
Signed-off-by: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
commit 10636bc2d60942254bda149827b922c41f4cb4af upstream.
The stations always chooses 1Mbps for all trasmitting frames,
whenever the AP is configured to lock the supported rates.
As the max phy rate is always set with the 4th from highest phy rate,
this assumption might be wrong if we have less than that. Fix that.
Cc: Paul Stewart <pstew@google.com>
Reported-by: Ajay Gummalla <agummalla@google.com>
Signed-off-by: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/net/wireless/ath/ath9k/rc.c | diffblobblamehistory |