linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net
Subject: Re: [PATCH] ath9k: Allow over-riding reg-domain.
Date: Mon, 11 Mar 2013 12:51:41 -0700	[thread overview]
Message-ID: <513E35CD.3010006@candelatech.com> (raw)
In-Reply-To: <20130311190537.GB32171@tuxdriver.com>

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.

Thanks,
Ben

>
> Do the Atheros folks have an opinion on this?
>
> John
>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2013-03-11 19:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11 16:45 [PATCH] ath9k: Allow over-riding reg-domain greearb
2013-03-11 19:05 ` John W. Linville
2013-03-11 19:51   ` Ben Greear [this message]
2013-03-11 20:08     ` John W. Linville
2013-03-11 20:17     ` Felix Fietkau
2013-03-11 21:01       ` Ben Greear
2013-03-11 21:36         ` Felix Fietkau
2013-03-11 21:44           ` Ben Greear
2013-03-11 21:51             ` Felix Fietkau
2013-03-11 22:00               ` Ben Greear
2013-03-11 22:07                 ` Felix Fietkau
2013-04-30 18:25       ` Ben Greear
  -- strict thread matches above, loose matches on Subject: below --
2013-03-11 22:45 Xose Vazquez Perez
2013-03-11 22:56 ` 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=513E35CD.3010006@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath9k-devel@venema.h4ckr.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).