> hmm, it seems we don't have a strict definition of mactime... the kerneldoc of > struct ieee80211_rx_status says: > * @mactime: MAC timestamp as defined by 802.11 Heh. > radiotap on the other hand defines it as the first bit of the data (MPDU): > * IEEE80211_RADIOTAP_TSFT u_int64_t microseconds > * > * Value in microseconds of the MAC's 64-bit 802.11 Time > * Synchronization Function timer when the first bit of the > * MPDU arrived at the MAC. For received frames, only. Yeah I think that makes most sense and is how it is usually implemented anyway. > so i guess right now it depends on the hardware what we actually get as > mactime... > do we have that information for other hardware? is mactime > *) the TSF at the reception of the first phy symbol? > *) the TSF at the reception of the first data (MPDU) symbol > *) the TSF at the reception of the byte 24 (where the timestamp field of > beacon and probe response frames is)? I very much doubt there is hardware that does the last option because there may be frames that are shorted than 24 bytes :) The difference between the first two options is a simple constant (depending on the PHY mode) so the driver for hardware that supports either one of those two options can easily translate them. Hence, I think we should declare it like radiotap does. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
