airbase: fix beacon interval timing #2177
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello. This pull request tries to fix up some of the beacon timing in airbase that I came across. Please let me know if there is anything I need to fixup to be accepted.
The current implementation had a few problems.
the time was 100 ms, and 5 ssids were beaconing, each ssid would beacon
every 500ms instead of every 100ms.
time (NTP adjustments and such).
frames are usually 100ms. A timer that takes into account small
amounts of jitter should be sufficient for beacon timing.
Tested with 50 ssids, on a ARMv7 @ 400mhz and didn't have any problem
keeping up. I saw jitter somewhere between 400us-1.5ms