On 18-7-2016 21:21, Arend Van Spriel wrote: > On 18-7-2016 21:15, Johannes Berg wrote: >> On Mon, 2016-07-18 at 21:13 +0200, Arend Van Spriel wrote: >>> >>> On 18-7-2016 20:56, Johannes Berg wrote: >>>> On Mon, 2016-07-18 at 19:23 +0530, Purushottam Kushwaha wrote: >>>>> Driver may allow support for different beacon interval on virtual >>>>> interfaces. >>>>> Allow if such support is advertised by driver. This adds new >>>>> ext_feature as NL80211_EXT_FEATURE_DIFF_BEACON_INTERVAL. >>>> >>>> We have NL80211_IFACE_COMB_STA_AP_BI_MATCH in interface >>>> combinations, >>>> perhaps it would make sense to also put this flag there? >>> >>> Hi Johannes, >>> >>> Was looking at the same thing. The description of that flag was a bit >>> unclear to me. >>> >>> """ >>> * @beacon_int_infra_match: In this combination, the beacon intervals >>> * between infrastructure and AP types must match. This is >>> required >>> * only in special cases. >>> """ >>> >>> It is not explicitly stated but it implies the STA vif is connected, >>> right. >> >> Yes. >> >> Forget this flag. I don't think any driver sets it - it was a hack for >> iwldvm. I also don't think any userspace cares about it, and it likely >> never really worked. What if the STA vif reconnects anyway? Uhm. My memory tells me differently and LXR also [1] :-p Regards, Arend [1] http://lxr.free-electrons.com/source/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c#L6182 -- 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
