All of lore.kernel.org
 help / color / mirror / Atom feed
From: John W. Linville <linville@tuxdriver.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: Allow over-riding reg-domain.
Date: Mon, 11 Mar 2013 15:05:38 -0400	[thread overview]
Message-ID: <20130311190537.GB32171@tuxdriver.com> (raw)
In-Reply-To: <1363020306-924-1-git-send-email-greearb@candelatech.com>

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?

Do the Atheros folks have an opinion on this?

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

WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville@tuxdriver.com>
To: greearb@candelatech.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 15:05:38 -0400	[thread overview]
Message-ID: <20130311190537.GB32171@tuxdriver.com> (raw)
In-Reply-To: <1363020306-924-1-git-send-email-greearb@candelatech.com>

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?

Do the Atheros folks have an opinion on this?

John
-- 
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:[~2013-03-11 19:05 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 ` John W. Linville [this message]
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         ` [ath9k-devel] " Felix Fietkau
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=20130311190537.GB32171@tuxdriver.com \
    --to=linville@tuxdriver.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.