ath9k: Update Beacon timers based on timestamp from the AP

Browse source

Some APs seem to drift away from the expected TBTT (timestamp %
beacon_int_in_usec differs quite a bit from zero) which can result in
us waking up way too early to receive a Beacon frame. In order to work
around this, re-configure the Beacon timers after having received a
Beacon frame from the AP (i.e., when we know the offset between the
expected TBTT and the actual time the AP is sending out the Beacon
frame).

Signed-off-by: Jouni Malinen <jouni.malinen@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>

...

This commit is contained in:

Jouni Malinen 2009-05-20 21:59:08 +03:00 • committed by John W. Linville

parent 267a901274

commit ccdfeab653

3 changed files with 16 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

1

drivers/net/wireless/ath/ath9k/ath9k.h

View file

9

drivers/net/wireless/ath/ath9k/main.c

View file

7

drivers/net/wireless/ath/ath9k/recv.c

View file