Benjamin Berg <benja...@sipsolutions.net> wrote: > From: Benjamin Berg <benjamin.b...@open-mesh.com> > > Beacons were not send out at (timestamp % beacon_time == 0) for interfaces > other than the primary one. To send out beacons with the correct timestamp > according to 10.1.3.2 of the 802.11 standard the tsf_adjustment has to be > set to the negative time difference instead of positive. This way the > later beacons get corrected to have a lower (and similar) timestamp with > regard to the beacon from slot 0. > > I am not aware about any issues that have been caused by this. > > Signed-off-by: Benjamin Berg <benjamin.b...@open-mesh.com>
Thanks, 6 patches applied to ath-next branch of ath.git: fa5106e1d793 ath9k: Correct TSF adjustment to align the beacon time correctly 9580cb889f35 ath9k: Handle channel context in get_/set_/reset_tsf bec9a94bc4e2 ath9k: Use tsf offset helper in ath9k_hw_reset 7fde51227aed ath9k: Expose tsf_adjustment in mac80211 tsf getters and setters. 11b0ac2e0c1c ath9k: Remove some #defined constants to decrease verbosity cfda2d8e2314 ath9k: Fix beacon configuration for addition/removal of interfaces -- Sent by pwcli https://patchwork.kernel.org/patch/9212535/ _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
