linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Question on 'iw reg get/set'
Date: Fri, 2 Jul 2010 12:48:00 -0400	[thread overview]
Message-ID: <20100702164759.GE2381@tuxdriver.com> (raw)
In-Reply-To: <4C2E170E.6040207@candelatech.com>

On Fri, Jul 02, 2010 at 09:42:54AM -0700, Ben Greear wrote:
> On 07/02/2010 07:12 AM, John W. Linville wrote:

> >The ath9k driver is setting its own regulatory restrictions based on
> >its EEPROM.  Setting the domain from userland can only further restrict
> >the regulatory settings.  The '98' value represents a synthesized
> >regulatory domain, based on the intersection of the available source
> >of regulatory information (which can include the EEPROM, the userland
> >setting, and a country IE from your AP).
> 
> Is there any way to get/set these raw settings (like, whatever it has in EEPROM)?
> 
> I expect we may ship some of these systems overseas, and would like the flexibility
> to set the country-code for testing purposes, if nothing else.

I'll leave it to the Atheros guys to address this.

> Is there any documentation as to what '98' really means, or do we just ignore that
> value and look at the info printed out after that?

'98' pretty much means "look at the info" :-)

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2010-07-02 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01 20:30 Question on 'iw reg get/set' Ben Greear
2010-07-02 14:12 ` John W. Linville
2010-07-02 16:42   ` Ben Greear
2010-07-02 16:48     ` John W. Linville [this message]
2010-07-03 16:35       ` Luis R. Rodriguez

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=20100702164759.GE2381@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.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 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).