On Mon, 2012-11-12 at 13:17 +0200, Jouni Malinen wrote: > Sorry for being a bit late with my comments, but does this single flag > really cover expected use cases? I would assume that number of more full > MAC -like designs will have to move to separate auth/assoc commands > instead of using connect API in the future (e.g., for FT and SAE). > However, those drivers do not necessarily expect user space to take care > of OBSS scans. I understand that this is not currently supported since > wpa_supplicant assuming auth/assoc to mean user space SME, but it should > be kept in mind that that may need to change in the future.. > > I guess we can handle the auth/assoc without user space OBSS scan > separately (a new feature flag for stopping OBSS scan?), so I'm fine > with this patch moving ahead as-is. Right, I don't see any other choice anyway given that we need to be backward compatible. I kinda scratched the surface of this previously when I said mac80211 could set the new flag, but then I don't see how to detect that it's explicitly not set vs. being an older kernel. johannes -- 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
