On Thu, 2012-04-12 at 09:41 +0200, Marco Porsch wrote: > > What time units would that be in, and how could you correlate them? > > I did not take an exhaustive overview over all possible drivers. > But as the current mac80211<->driver interface carries only beacon > interval (in TU) and DTIM period, that should be a good starting point. Those aren't really useful at all? You need to define wakeups in absolute terms I'd think? And you could have the TSF from the beacon, but that itself is also useless since you need the offset. > ath9k additionally relies on the neighbors address to check whether it > can resume sleep after receiving an expected beacon (see setting of > 'is_mybeacon' in ath_rx_tasklet). That's IBSS only I'd think? > Concerning correlation, in mesh mode we recently have t_offset (in TSF > increments) stored in sta_info and in client mode the drivers' > synchronised TSF should be the reference (but I am not quite sure what > happens when one client is associated to multiple AP). That's starting to sound more like a solution, but even then you have a lot of issues to resolve like when exactly is the timestamp hitting. Keep in mind that TSF == start of TSF field, while rx_status->timestamp == start of first symbol, which I didn't even remember when you guys did all the Toffset things, I'm guessing they're all wrong :-) johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
