tree 7f7dbc8c88d7cb31ec280d2c1fc486249ea97aec
parent ed9d01026f156db2d638cbb045231c7a8fde877d
author Felix Fietkau <nbd@openwrt.org> 1305580920 +0200
committer John W. Linville <linville@tuxdriver.com> 1305827634 -0400

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>