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 database. If the >> band >> is not present there, the channels are simply disabled. > > I can see why you'd want this flag internally (although it'll require > rework given the comments on the previous patch) - but is there a > reason to export it in nl80211? I don't see any reason either. Only all regulatory rule flags (nl80211_reg_rule_flags) happen to be "exported". Shall I add new field (e.g. internal_flags) to struct ieee80211_reg_rule and define new enum for it? > Then again, perhaps it *would* be good to show this information in > userspace? 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()? -Michal -- 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
