On Tue, 2015-01-13 at 09:35 +0100, Janusz Dziedzic wrote: > +++ b/net/mac80211/main.c > @@ -549,6 +549,7 @@ struct ieee80211_hw *ieee80211_alloc_hw_nm(size_t priv_data_len, > wiphy->features |= NL80211_FEATURE_LOW_PRIORITY_SCAN | > NL80211_FEATURE_AP_SCAN; > > + wiphy_ext_feature_set(wiphy, NL80211_FEATURE_VHT_IBSS); Maybe we should leave this to the driver? And it should certainly depend on actual VHT capability, I'd say? Seems confusing if we ended up with a driver that doesn't have VHT but says it has VHT_IBSS :) > +++ b/net/mac80211/util.c > @@ -2329,6 +2329,41 @@ u8 *ieee80211_ie_build_ht_oper(u8 *pos, struct ieee80211_sta_ht_cap *ht_cap, > return pos + sizeof(struct ieee80211_ht_operation); > } > > +u8 *ieee80211_ie_build_vht_oper(u8 *pos, struct ieee80211_sta_vht_cap *vht_cap, > + const struct cfg80211_chan_def *chandef) For now that'll only be used by IBSS (perhaps mesh in the future?), but maybe it should just be in ibss.c until it's used more? 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
