From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: Allow over-riding reg-domain.
Date: Mon, 11 Mar 2013 22:36:54 +0100 [thread overview]
Message-ID: <513E4E76.2000000@openwrt.org> (raw)
In-Reply-To: <513E4617.2020906@candelatech.com>
On 2013-03-11 10:01 PM, Ben Greear wrote:
> On 03/11/2013 01:17 PM, Felix Fietkau wrote:
>> On 2013-03-11 8:51 PM, Ben Greear wrote:
>>> On 03/11/2013 12:05 PM, John W. Linville wrote:
>>>> On Mon, Mar 11, 2013 at 09:45:06AM -0700, greearb at candelatech.com wrote:
>>>>> From: Ben Greear <greearb@candelatech.com>
>>>>>
>>>>> Otherwise, can't get the Sparklan AR9380 NICs to be
>>>>> 5Ghz APs, since they are in world-roaming domain by
>>>>> default. Add this to /etc/modprobe.d/ath9k.conf:
>>>>>
>>>>> options ath9k override_eeprom_regdomain=0
>>>>>
>>>>> Signed-off-by: Ben Greear <greearb@candelatech.com>
>>>>
>>>> Why "=0" to enable it? Just to make it more confusing?
>>>
>>> You are just setting the country code...and country-code 0 seems
>>> to at least open up the US regulatory domain so we use it
>>> by default.
>>>
>>> You can use any country code you wish here.
>> I'd like to have less fugly module parameter hackery please. How about
>> either using CONFIG_CFG80211_CERTIFICATION_ONUS the way it was intended,
>> or adding another config option that makes it bail out of
>> ath_regd_init_wiphy() early, thus still processing the EEPROM regdomain
>> hint and not making it binding.
>
> I am not sure what you are suggesting. I enabled this override
> only when ONUS is selected because I wanted it clear that users
> were taking their regulatory compliance into their own hands.
And as far as I understand, CONFIG_CFG80211_CERTIFICATION_ONUS already
enables some code in cfg80211 that allows a special type of regulatory
change request from user space that bypasses intersection.
> I always want the module option at least visible so that
> you don't have to muck with modprobe.conf just to get ath9k.ko
> to load when it's compiled differently.
>
> For the second part, you want the ability to set the regdomain
> be a compile-time option like CONFIG_ATH9K_OVERRIDE_REGDOMAIN
> or something like that?
Something like that, yes. It should depend on
CONFIG_CFG80211_CERTIFICATION_ONUS and should contain a help text that
strongly discourages any distribution from enabling it in their kernel
builds.
- Felix
WARNING: multiple messages have this Message-ID (diff)
From: Felix Fietkau <nbd@openwrt.org>
To: Ben Greear <greearb@candelatech.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net
Subject: Re: [PATCH] ath9k: Allow over-riding reg-domain.
Date: Mon, 11 Mar 2013 22:36:54 +0100 [thread overview]
Message-ID: <513E4E76.2000000@openwrt.org> (raw)
In-Reply-To: <513E4617.2020906@candelatech.com>
On 2013-03-11 10:01 PM, Ben Greear wrote:
> On 03/11/2013 01:17 PM, Felix Fietkau wrote:
>> On 2013-03-11 8:51 PM, Ben Greear wrote:
>>> On 03/11/2013 12:05 PM, John W. Linville wrote:
>>>> On Mon, Mar 11, 2013 at 09:45:06AM -0700, greearb@candelatech.com wrote:
>>>>> From: Ben Greear <greearb@candelatech.com>
>>>>>
>>>>> Otherwise, can't get the Sparklan AR9380 NICs to be
>>>>> 5Ghz APs, since they are in world-roaming domain by
>>>>> default. Add this to /etc/modprobe.d/ath9k.conf:
>>>>>
>>>>> options ath9k override_eeprom_regdomain=0
>>>>>
>>>>> Signed-off-by: Ben Greear <greearb@candelatech.com>
>>>>
>>>> Why "=0" to enable it? Just to make it more confusing?
>>>
>>> You are just setting the country code...and country-code 0 seems
>>> to at least open up the US regulatory domain so we use it
>>> by default.
>>>
>>> You can use any country code you wish here.
>> I'd like to have less fugly module parameter hackery please. How about
>> either using CONFIG_CFG80211_CERTIFICATION_ONUS the way it was intended,
>> or adding another config option that makes it bail out of
>> ath_regd_init_wiphy() early, thus still processing the EEPROM regdomain
>> hint and not making it binding.
>
> I am not sure what you are suggesting. I enabled this override
> only when ONUS is selected because I wanted it clear that users
> were taking their regulatory compliance into their own hands.
And as far as I understand, CONFIG_CFG80211_CERTIFICATION_ONUS already
enables some code in cfg80211 that allows a special type of regulatory
change request from user space that bypasses intersection.
> I always want the module option at least visible so that
> you don't have to muck with modprobe.conf just to get ath9k.ko
> to load when it's compiled differently.
>
> For the second part, you want the ability to set the regdomain
> be a compile-time option like CONFIG_ATH9K_OVERRIDE_REGDOMAIN
> or something like that?
Something like that, yes. It should depend on
CONFIG_CFG80211_CERTIFICATION_ONUS and should contain a help text that
strongly discourages any distribution from enabling it in their kernel
builds.
- Felix
next prev parent reply other threads:[~2013-03-11 21:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 16:45 [ath9k-devel] [PATCH] ath9k: Allow over-riding reg-domain greearb at candelatech.com
2013-03-11 16:45 ` greearb
2013-03-11 19:05 ` [ath9k-devel] " John W. Linville
2013-03-11 19:05 ` John W. Linville
2013-03-11 19:51 ` [ath9k-devel] " Ben Greear
2013-03-11 19:51 ` Ben Greear
2013-03-11 20:08 ` [ath9k-devel] " John W. Linville
2013-03-11 20:08 ` John W. Linville
2013-03-11 20:17 ` [ath9k-devel] " Felix Fietkau
2013-03-11 20:17 ` Felix Fietkau
2013-03-11 21:01 ` [ath9k-devel] " Ben Greear
2013-03-11 21:01 ` Ben Greear
2013-03-11 21:36 ` Felix Fietkau [this message]
2013-03-11 21:36 ` Felix Fietkau
2013-03-11 21:44 ` [ath9k-devel] " Ben Greear
2013-03-11 21:44 ` Ben Greear
2013-03-11 21:51 ` [ath9k-devel] " Felix Fietkau
2013-03-11 21:51 ` Felix Fietkau
2013-03-11 22:00 ` [ath9k-devel] " Ben Greear
2013-03-11 22:00 ` Ben Greear
2013-03-11 22:07 ` [ath9k-devel] " Felix Fietkau
2013-03-11 22:07 ` Felix Fietkau
2013-04-30 18:25 ` [ath9k-devel] " Ben Greear
2013-04-30 18:25 ` Ben Greear
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=513E4E76.2000000@openwrt.org \
--to=nbd@openwrt.org \
--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.