From: Johannes Berg <johannes@sipsolutions.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH v2 6/8] cfg80211: reg: Add NL80211_RRF_USER_REGD_NEEDED flag
Date: Fri, 27 Nov 2015 09:35:16 +0100 [thread overview]
Message-ID: <1448613316.2531.13.camel@sipsolutions.net> (raw)
In-Reply-To: <1448303241-27747-7-git-send-email-sojkam1@fel.cvut.cz> (sfid-20151123_192804_844242_D8C85F7B)
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? Then again, perhaps it *would* be good
to show this information in userspace?
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Sojka <sojkam1@fel.cvut.cz>, linux-wireless@vger.kernel.org
Cc: bernd.lehmann@volkswagen.de, s.sander@nordsys.de,
wireless-regdb@lists.infradead.org, ath9k-devel@lists.ath9k.org,
ath9k-devel@qca.qualcomm.com,
"Jan Kaisrlík" <kaisrja1@fel.cvut.cz>
Subject: Re: [PATCH v2 6/8] cfg80211: reg: Add NL80211_RRF_USER_REGD_NEEDED flag
Date: Fri, 27 Nov 2015 09:35:16 +0100 [thread overview]
Message-ID: <1448613316.2531.13.camel@sipsolutions.net> (raw)
In-Reply-To: <1448303241-27747-7-git-send-email-sojkam1@fel.cvut.cz> (sfid-20151123_192804_844242_D8C85F7B)
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? Then again, perhaps it *would* be good
to show this information in userspace?
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Sojka <sojkam1@fel.cvut.cz>, linux-wireless@vger.kernel.org
Cc: "Jan Kaisrlík" <kaisrja1@fel.cvut.cz>,
wireless-regdb@lists.infradead.org, ath9k-devel@qca.qualcomm.com,
ath9k-devel@lists.ath9k.org, bernd.lehmann@volkswagen.de,
s.sander@nordsys.de
Subject: Re: [wireless-regdb] [PATCH v2 6/8] cfg80211: reg: Add NL80211_RRF_USER_REGD_NEEDED flag
Date: Fri, 27 Nov 2015 09:35:16 +0100 [thread overview]
Message-ID: <1448613316.2531.13.camel@sipsolutions.net> (raw)
In-Reply-To: <1448303241-27747-7-git-send-email-sojkam1@fel.cvut.cz>
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? Then again, perhaps it *would* be good
to show this information in userspace?
johannes
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next prev parent reply other threads:[~2015-11-27 8:35 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 18:27 [PATCH v2 0/8] Regulatory and ath9k support for ITS-G5 band (5.9 GHz) Michal Sojka
2015-11-23 18:28 ` [ath9k-devel] " Michal Sojka
2015-11-23 18:27 ` [wireless-regdb] " Michal Sojka
2015-11-23 18:27 ` [PATCH v2 1/8] cfg80211: reg: Remove unused function parameter Michal Sojka
2015-11-23 18:28 ` [ath9k-devel] " Michal Sojka
2015-11-23 18:27 ` [wireless-regdb] " Michal Sojka
2015-11-23 18:27 ` [PATCH v2 2/8] cfg80211: Remove unused cfg80211_can_use_iftype_chan() Michal Sojka
2015-11-23 18:28 ` [ath9k-devel] " Michal Sojka
2015-11-23 18:27 ` [wireless-regdb] " Michal Sojka
2015-11-26 16:46 ` [ath9k-devel] " Johannes Berg
2015-11-26 16:46 ` [wireless-regdb] " Johannes Berg
2015-11-26 16:46 ` Johannes Berg
2015-11-23 18:27 ` [PATCH v2 3/8] cfg80211: reg: Refactor calculation of bandwidth flags Michal Sojka
2015-11-23 18:28 ` [ath9k-devel] " Michal Sojka
2015-11-23 18:27 ` [wireless-regdb] " Michal Sojka
2015-11-26 17:48 ` [ath9k-devel] " Johannes Berg
2015-11-26 17:48 ` [wireless-regdb] " Johannes Berg
2015-11-26 17:48 ` Johannes Berg
2015-11-23 18:27 ` [PATCH v2 4/8] cfg80211: reg: Properly handle rules for 5 and 10 MHz channels Michal Sojka
2015-11-23 18:28 ` [ath9k-devel] " Michal Sojka
2015-11-23 18:27 ` [wireless-regdb] " Michal Sojka
2015-11-26 17:51 ` [ath9k-devel] " Johannes Berg
2015-11-26 17:51 ` [wireless-regdb] " Johannes Berg
2015-11-26 17:51 ` Johannes Berg
2015-11-30 9:56 ` [ath9k-devel] " Jouni Malinen
2015-11-30 9:56 ` [wireless-regdb] " Jouni Malinen
2015-11-30 9:56 ` Jouni Malinen
2015-11-30 10:30 ` [ath9k-devel] " Johannes Berg
2015-11-30 10:30 ` [wireless-regdb] " Johannes Berg
2015-11-30 10:30 ` Johannes Berg
2015-11-23 18:27 ` [PATCH v2 5/8] cfg80211: Add support for OCB-only channels Michal Sojka
2015-11-23 18:28 ` [ath9k-devel] " Michal Sojka
2015-11-23 18:27 ` [wireless-regdb] " Michal Sojka
2015-11-27 8:33 ` [ath9k-devel] " Johannes Berg
2015-11-27 8:33 ` [wireless-regdb] " Johannes Berg
2015-11-27 8:33 ` Johannes Berg
2015-11-27 8:59 ` Michal Sojka
2015-11-27 8:59 ` [ath9k-devel] " Michal Sojka
2015-11-27 8:59 ` [wireless-regdb] " Michal Sojka
2015-11-23 18:27 ` [PATCH v2 6/8] cfg80211: reg: Add NL80211_RRF_USER_REGD_NEEDED flag Michal Sojka
2015-11-23 18:28 ` [ath9k-devel] " Michal Sojka
2015-11-23 18:27 ` [wireless-regdb] " Michal Sojka
2015-11-27 8:35 ` Johannes Berg [this message]
2015-11-27 8:35 ` Johannes Berg
2015-11-27 8:35 ` Johannes Berg
2015-11-27 9:43 ` Michal Sojka
2015-11-27 9:44 ` [ath9k-devel] " Michal Sojka
2015-11-27 9:43 ` [wireless-regdb] " Michal Sojka
2015-11-27 9:52 ` [ath9k-devel] " Johannes Berg
2015-11-27 9:52 ` [wireless-regdb] " Johannes Berg
2015-11-27 9:52 ` Johannes Berg
2015-11-23 18:27 ` [PATCH v2 7/8] cfg80211: Add Kconfig option for ITS-G5 band (5.9 GHz) Michal Sojka
2015-11-23 18:28 ` [ath9k-devel] " Michal Sojka
2015-11-23 18:27 ` [wireless-regdb] " Michal Sojka
2015-11-26 17:55 ` [ath9k-devel] " Johannes Berg
2015-11-26 17:55 ` [wireless-regdb] " Johannes Berg
2015-11-26 17:55 ` Johannes Berg
2015-11-26 21:10 ` Michal Sojka
2015-11-26 21:11 ` [ath9k-devel] " Michal Sojka
2015-11-26 21:10 ` [wireless-regdb] " Michal Sojka
2015-11-27 8:25 ` [ath9k-devel] " Johannes Berg
2015-11-27 8:25 ` [wireless-regdb] " Johannes Berg
2015-11-27 8:25 ` Johannes Berg
2015-11-27 8:44 ` Michal Sojka
2015-11-27 8:44 ` [ath9k-devel] " Michal Sojka
2015-11-27 8:44 ` [wireless-regdb] " Michal Sojka
2015-11-23 18:27 ` [PATCH v2 8/8] ath9k: Add support " Michal Sojka
2015-11-23 18:28 ` [ath9k-devel] " Michal Sojka
2015-11-23 18:27 ` [wireless-regdb] " Michal Sojka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1448613316.2531.13.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.