Johannes Berg <johannes@xxxxxxxxxxxxxxxx> writes: > However, I think it's indicative of a bigger problem. I gave it some > thought, and came to the conclusion that it previously didn't happen > because we always won the race. Let me explain. One more reason why need to receive the beacon is synchronisation to the beacon for power save. For example wl1251 and wl1271 want to receive one beacon for synchronisation purposes before some of the commands are executed. It would be really nice if mac80211 would take care of that. > First, we could go back to the original behaviour if we have just one > virtual interface. I think this is good to have. Just to keep it simple for devices like wl1251 and wl1271. > But that still leaves us with the race, we might do all three frame > exchanges within a beacon interval and still miss the beacon, we > just tend to not do that and get a beacon. > > The other solution I see is that we add a new step before or after the > direct probe step, which would just be "wait for a beacon". This would > ensure we have both probe and beacon information always ready. It would > also ensure we have both probe and beacon info for our new userspace > reporting of that. I like this. If only the bssid would be provided to the driver before the association process, both wl1251 and wl1271 would not have to worry about firmware beacon synchronisation. -- Kalle Valo -- 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
