On 08/14/2017 01:13 PM, Grumbach, Emmanuel wrote:
It is kind of not clear right now for drivers where to get
information from:
- NL attributes passed from userspace and forwarded to a driver
Since those exist, it seems to make more sense to me to use those
rather than any in-driver decided policy. Usually, deciding upon
policies from lower levels is frowned upon I'd say.
I agree, what I mean is that drivers should know where to take this
information from, if there are multiple sources.
An example are HT/VHT capabilities for start_ap command: they can be
parsed directly by drivers by looking at beacon's IEs in
"cfg80211_ap_settings". At the same time those are also parsed by
nl80211 which fills cfg80211_ap_settings::ht_cap,
cfg80211_ap_settings::vht_cap.
Why HT/VHT caps are not passed directly from usespace as one of NL
attributes? I guess because there is not much point in it since
userspace passes entire IE set anyway, which can be used by lower levels.
- IEs passed from userspace, parsed by nl80211 and forwarded to a
driver
- IEs that are passed from userspace and parsed by drivers directly
Thanks,
Arend
