Re: [PATCH v2 6/8] cfg80211: reg: Add NL80211_RRF_USER_REGD_NEEDED flag

2015-11-27 Thread Johannes Berg
On Fri, 2015-11-27 at 10:43 +0100, Michal Sojka wrote: > What do you mean by "show"? nl80211_put_regdom() already sends regdom > flags to userspace. Or do you mean introducing a new channel > attribute and send it in nl80211_msg_put_channel()? > No, I meant keeping the flag - so that people can

Re: [PATCH v2 6/8] cfg80211: reg: Add NL80211_RRF_USER_REGD_NEEDED flag

2015-11-27 Thread Michal Sojka
On Fri, Nov 27 2015, Johannes Berg wrote: > On Mon, 2015-11-23 at 19:27 +0100, Michal Sojka wrote: >>  >> The NL80211_RRF_USER_REGD_NEEDED flag introduced in this commit >> allows >> drivers to specify that certain band is enabled only if it is >> additionally enabled in user-supplied regulatory da

Re: [PATCH v2 6/8] cfg80211: reg: Add NL80211_RRF_USER_REGD_NEEDED flag

2015-11-27 Thread Johannes Berg
On Mon, 2015-11-23 at 19:27 +0100, Michal Sojka wrote: >  > The NL80211_RRF_USER_REGD_NEEDED flag introduced in this commit > allows > drivers to specify that certain band is enabled only if it is > additionally enabled in user-supplied regulatory database. If the > band > is not present there, the

[PATCH v2 6/8] cfg80211: reg: Add NL80211_RRF_USER_REGD_NEEDED flag

2015-11-23 Thread Michal Sojka
In order to prevent accidental use of Intelligent Transportation System band (5.9 GHz), we require system integrators to provide custom userspace regulatory database enabling the use of the band. However, drivers that provide their own regulatory database (such as ath9k) would not enable that band