Johannes Berg wrote: > That looks a bit different from what I thought though? Not really sure I > understand that though :-) The basic issue was that we were not initializing the timers based on the sync'd TSF. > What I'm thinking is that if you always just start beaconing, wouldn't > you just reset the beacon whenever you notice a higher TSF show up in > the network? > > Actually I think we call reset_tsf() or something like that? But all of > that has always seemed very quirky to me. Currently, I don't think we reset the beacon/timers for IBSS mode. For station mode, all of this is handled in ath9k using the PS_WAIT_FOR_BEACON/PS_BEACON_SYNC flags. For IBSS creator mode, there is no problem because mac80211 calls reset_tsf() in __ieee80211_sta_join_ibss(). For joiner mode, drivers like ath9k need to do a beacon-sync (like station), before starting to pollute the environment with beacons, but there is no way to know if an existing IBSS network is being joined. Sujith -- 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
