Hi Jouni! > I agree that merge part (updating Beacon/ProbeRsp data) can be skipped > for same BSSID, but this change seems to break timesync by removing call > to local->ops->reset_tsf(). I don't think that that should be removed > unconditionally. Thanks for your comment. > I would like to know whether that operation is causing > any problems in citywide networks and if yes, it might be better to > provide a configuration option to allow the timesync for IBSS to be > disabled since not doing that could cause problems to power saving in > IBSS (not that it is really implemented that widely). As I see, only the sta_info_flush_delayed() call causes the problems. I can only disable this call in the ieee80211_sta_join_ibss() function, if the BSSID is the same. Do you think this would be better? > In other words, I would be fine if the calls to > ieee80211_sta_join_ibss() and ieee80211_ibss_add_sta() are replaced with > local->ops->reset_tsf() if BSSIDs are the same when > beacon_timestamp>rx_timestamp. This would be a way, too. Regards Alina -- Sensationsangebot verlängert: GMX FreeDSL - Telefonanschluss + DSL für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K1308T4569a -- 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
