Mon, Jul 14, 2025 at 02:50:42PM +0200, Johannes Berg wrote: > Hi, > > So just to say this up front I have very little interest per se in this > feature directly, so I'll mostly leave it to you :) Hi Johannes, Firstly appreciate the thorough and quick reply... and of course that is fine. We still want to make sure we implement it correctly :) > > 11.1.3.10.2: > > > > "The value for the dot11ShortBeaconPeriod shall be such that > > dot11BeaconPeriod = n * dot11ShortBeaconPeriod, where n is a > > positive integer. This defines a series of TSBTTs exactly > > dot11ShortBeaconPeriod TUs apart" > > > > the value for n here is what we are denoting as > > s1g_short_beacon_period (another deviation from the naming > > within the standard) which represents the number of short > > beacons between each long beacon. > > That seems slightly confusing - I've have interpreted a 'period' either > as a span of time (as in the spec), or the number of steps between > events, so maybe that's rather 's1g_long_beacon_period'? But if the spec > uses period as a span of time, then perhaps 's1g_long_beacon_step' or > something would be easier to understand? Not sure ... You are right, it should be the long beacon period (similar to how the DTIM period describes the number of intervals between each DTIM beacon). lachlan
