diff options
| author | Felix Fietkau <nbd@openwrt.org> | 2011-05-16 17:22:00 -0400 |
|---|---|---|
| committer | John W. Linville <linville@tuxdriver.com> | 2011-05-19 13:53:54 -0400 |
| commit | c6820f1e6c8273ca4b8f94c2354193d19e1a5c47 (patch) | |
| tree | 7f7dbc8c88d7cb31ec280d2c1fc486249ea97aec /net/rfkill/Kconfig | |
| parent | ed9d01026f156db2d638cbb045231c7a8fde877d (diff) | |
ath9k: fix ad-hoc mode beacon selection
In ad-hoc mode, beacon timers are configured differently compared to AP
mode, and (depending on the scenario) can vary enough to make the beacon
tasklet not detect slot 0 based on the TSF.
Since staggered beacons are not (and cannot be) used in ad-hoc mode, it
makes more sense to just hardcode slot 0 here, avoiding unnecessary
TSF reads and calculations.
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Reported-by: Rajkumar Manoharan <rmanoharan@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'net/rfkill/Kconfig')
0 files changed, 0 insertions, 0 deletions