Hello Jouni! > Some hardware designs require the reset_tsf call to allow the hardware > to get back in sync with the TSF based on received timestamp values in > some cases. I would expect this to be used in ath9k and ath5k. This does > not mean that the timestamp would be reset to zero in actual Beacon > frames, i.e., this is just something done internally in the > driver/firmware/hardware and the need for reset_tsf() is to just provide > the notification to the driver when this special case is needed. Okay, thanks for your notice. Than I think the dummy merge detection code should in the ieee80211_sta_join_ibss() function and if so only call reset_tsf()?! Should it make any other thinks too in this case? Regards Alina -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger -- 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