From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Allow over-riding regdomain in NIC when CFG80211_CERTIFICATION_ONUS is enabled?
Date: Tue, 04 Dec 2012 09:06:12 -0800 [thread overview]
Message-ID: <50BE2D84.4010809@candelatech.com> (raw)
In-Reply-To: <CAB=NE6XQGKTFq_yQt7QuFmozNCDT42w7B8qSdv_FY4arOQziZg@mail.gmail.com>
On 12/03/2012 03:16 PM, Luis R. Rodriguez wrote:
> On Mon, Dec 3, 2012 at 2:44 PM, Ben Greear <greearb@candelatech.com> wrote:
>> There are out-of-tree patches for ath9k (at least) that allow overriding the
>> eeprom reg domain via a module option.
>>
>> Any chance something like that could make it upstream if it were dependent
>> on CFG80211_CERTIFICATION_ONUS?
>>
>> (We recently got a batch of wpea-127n NICs with country-code of TW, which
>> reminded me of this problem).
>
> I think it would be reasonable, but note Adrian's points. We likely
> would need then only to be able to change regulatory domains for only
> regulatory domains that match the CTLs programmed in. I'll also note
> that the default CTL is actually a high value rather than no
> transmit...
How do I get this information? What is a CTL anyway?
Thanks,
Ben
>
> Luis
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>
Subject: Re: Allow over-riding regdomain in NIC when CFG80211_CERTIFICATION_ONUS is enabled?
Date: Tue, 04 Dec 2012 09:06:12 -0800 [thread overview]
Message-ID: <50BE2D84.4010809@candelatech.com> (raw)
In-Reply-To: <CAB=NE6XQGKTFq_yQt7QuFmozNCDT42w7B8qSdv_FY4arOQziZg@mail.gmail.com>
On 12/03/2012 03:16 PM, Luis R. Rodriguez wrote:
> On Mon, Dec 3, 2012 at 2:44 PM, Ben Greear <greearb@candelatech.com> wrote:
>> There are out-of-tree patches for ath9k (at least) that allow overriding the
>> eeprom reg domain via a module option.
>>
>> Any chance something like that could make it upstream if it were dependent
>> on CFG80211_CERTIFICATION_ONUS?
>>
>> (We recently got a batch of wpea-127n NICs with country-code of TW, which
>> reminded me of this problem).
>
> I think it would be reasonable, but note Adrian's points. We likely
> would need then only to be able to change regulatory domains for only
> regulatory domains that match the CTLs programmed in. I'll also note
> that the default CTL is actually a high value rather than no
> transmit...
How do I get this information? What is a CTL anyway?
Thanks,
Ben
>
> Luis
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2012-12-04 17:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 22:44 [ath9k-devel] Allow over-riding regdomain in NIC when CFG80211_CERTIFICATION_ONUS is enabled? Ben Greear
2012-12-03 22:44 ` Ben Greear
2012-12-03 22:48 ` [ath9k-devel] " Adrian Chadd
2012-12-03 22:48 ` Adrian Chadd
2012-12-03 22:50 ` [ath9k-devel] " Ben Greear
2012-12-03 22:50 ` Ben Greear
2012-12-03 23:16 ` [ath9k-devel] " Luis R. Rodriguez
2012-12-03 23:16 ` Luis R. Rodriguez
2012-12-04 17:06 ` Ben Greear [this message]
2012-12-04 17:06 ` Ben Greear
2012-12-04 19:45 ` [ath9k-devel] " Adrian Chadd
2012-12-04 19:45 ` Adrian Chadd
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=50BE2D84.4010809@candelatech.com \
--to=greearb@candelatech.com \
--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.