Commit 1008e0f7 authored by Bruno Randolf's avatar Bruno Randolf Committed by David S. Miller

ath5k: use 3 instead of 0x00000003

reviewed beacon timer initialization with register traces from madwifi: what we
are doing is correct :). one minor fix: use 3 instead of 0x00000003 - it's more
readable.

drivers/net/wireless/ath5k/hw.c:        Changes-licensed-under: ISC
Signed-off-by: default avatarBruno Randolf <bruno@thinktube.com>
Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
parent 1f7d87b0
...@@ -2605,10 +2605,8 @@ void ath5k_hw_init_beacon(struct ath5k_hw *ah, u32 next_beacon, u32 interval) ...@@ -2605,10 +2605,8 @@ void ath5k_hw_init_beacon(struct ath5k_hw *ah, u32 next_beacon, u32 interval)
break; break;
default: default:
timer1 = (next_beacon - AR5K_TUNE_DMA_BEACON_RESP) << timer1 = (next_beacon - AR5K_TUNE_DMA_BEACON_RESP) << 3;
0x00000003; timer2 = (next_beacon - AR5K_TUNE_SW_BEACON_RESP) << 3;
timer2 = (next_beacon - AR5K_TUNE_SW_BEACON_RESP) <<
0x00000003;
} }
timer3 = next_beacon + (ah->ah_atim_window ? ah->ah_atim_window : 1); timer3 = next_beacon + (ah->ah_atim_window ? ah->ah_atim_window : 1);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment