| commit | c1fada4e5e53d88a8edd3ff01cee9d316cbf6025 | |
| author | Gabor Juhos <juhosg@openwrt.org> | |
| Sat, 17 Aug 2013 12:09:28 +0000 (17 14:09 +0200) | ||
| committer | John W. Linville <linville@tuxdriver.com> | |
| Thu, 22 Aug 2013 18:30:26 +0000 (22 14:30 -0400) | ||
| tree | f3a328db0f5487d32fb5128e9816521c8286e7da | treesnapshot (tar.gz zip) |
| parent | 77f7c0f3b8f2d464e841c5c35f3da8b4999a885c | commitdiff |
rt2x00: rt2800lib: fix frequency offset boundary calculation
The current code in the 'rt2800_adjust_freq_offset'
function limits the device specific frequency offset
value to FREQ_BOUND but ignores the fact that the
uppermost bit is not part of the frequency offset
value. As the result, the driver always uses the
FREQ_BOUND value if the uppermost bit is set.
Update the code to use the correct source value
for calculating the boundary.
Based on the DPO_RT5572_LinuxSTA_2.6.0.1_20120629
driver.
Reference:
RTMPAdjustFrequencyOffset function in common/rt_rf.c
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
The current code in the 'rt2800_adjust_freq_offset'
function limits the device specific frequency offset
value to FREQ_BOUND but ignores the fact that the
uppermost bit is not part of the frequency offset
value. As the result, the driver always uses the
FREQ_BOUND value if the uppermost bit is set.
Update the code to use the correct source value
for calculating the boundary.
Based on the DPO_RT5572_LinuxSTA_2.6.0.1_20120629
driver.
Reference:
RTMPAdjustFrequencyOffset function in common/rt_rf.c
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
| drivers/net/wireless/rt2x00/rt2800lib.c | diffblobblamehistory |