hello!
this is just a RFC for my description of some problems we have with the rx
timestamp (we don't know when it is taken exactly) and my attempt to fix one
problem we have when we get an invalid beacon rx timestamp. it seems like i'm
able to trigger this problem reliably by sending beacons with a length bigger
than 74 bytes.
please tell me what you think about this.
benoit, this is ath5k stuff, but i thought it might interrest you anyways and
you might have something to add...
thanks,
bruno
---
Bruno Randolf (2):
ath5k: fix beacon rx timestamp in IBSS mode
ath5k: add notes about rx timestamp
drivers/net/wireless/ath5k/base.c | 59 +++++++++++++++++++++++++++++++------
1 files changed, 50 insertions(+), 9 deletions(-)
--
Signature
_______________________________________________
ath5k-devel mailing list
[email protected]
https://lists.ath5k.org/mailman/listinfo/ath5k-devel
