On Tue, 2019-06-25 at 13:21 +0300, Alexei Lazar wrote: > > > > * @NL80211_BAND_ATTR_VHT_CAPA: VHT capabilities, as in the HT > > > information IE > > > * @NL80211_BAND_ATTR_IFTYPE_DATA: nested array attribute, with each > > > entry using > > > * attributes from &enum nl80211_band_iftype_attr > > > + * @NL80211_BAND_ATTR_EDMG_CHANNELS: bitmap that indicates the 2.16 > > > GHz > > > + * channel(s) that are allowed to be used for EDMG transmissions > > > in > > > the > > > + * BSS as defined by IEEE 802.11 section 9.4.2.251. > > > + * @NL80211_BAND_ATTR_EDMG_BW_CONFIG: Channel BW Configuration > > > subfield > > > + * encodes the allowed channel bandwidth configurations as defined > > > by > > > + * IEEE 802.11 section 9.4.2.251, Table 13. > > > * @NL80211_BAND_ATTR_MAX: highest band attribute currently defined > > > * @__NL80211_BAND_ATTR_AFTER_LAST: internal use > > > > And ... that makes more sense than the global attribute I guess? > > We feel it belongs to the BAND attributes because for example also VHT > capability is there. There are however 2 other options: > 1. Move the attribute to the NL80211_FREQUENCY_ATTR > 2. Move them to the global attributes > Any preference?
I think I just got confused. Is this used for capability reporting then? I guess that'd make sense here, yeah. johannes
