Hi, On 20 October 2012 19:32, Thomas Pedersen <thomas@xxxxxxxxxxx> wrote: > Hi list, > > We're seeing some issue with reported mactime by the ath9k_htc (AR9271) > card. Here is a mesh node sampling peer beacons: > [snip] > The number after "at" is rx_status->mactime, "now" is drv_get_tsf(), and > offset (ie. stack delay) is mactime - tsf. RX_FLAG_MACTIME_MPDU is on for > all frames, and mesh sync is not adjusting the TSF. > > How can we possibly receive frames from the future!? > 1) Are you correctly merging the TSF32 values? Are you comparing TSF32 to TSF64, are you converting 32->64, etc? TSF32 wraps pretty quickly and there's some kooky logic needed to make sure your TSF64 calculated value is correct. 2) Are all your mesh nodes synchronised? Why don't you print out the timestamp inside the beacon frame as well, and compare whether they're all in reasonable sync? Adrian -- 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
