From: "John W. Linville" <linville@tuxdriver.com>
To: Chris Clayton <chris2553@googlemail.com>
Cc: Frans Pop <elendil@planet.nl>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
mcgrof@gmail.com
Subject: Re: ath5k - strange regulatory domain change
Date: Fri, 7 Aug 2009 11:16:47 -0400 [thread overview]
Message-ID: <20090807151304.GE7545@tuxdriver.com> (raw)
In-Reply-To: <c6b1100b0908070757t7b973180s17959e0f46347d5d@mail.gmail.com>
On Fri, Aug 07, 2009 at 03:57:30PM +0100, Chris Clayton wrote:
> 2009/8/7 John W. Linville <linville@tuxdriver.com>:
> > On Fri, Aug 07, 2009 at 01:56:43PM +0100, Chris Clayton wrote:
> >> To sum this up then (as I understand things):
> >>
> >> 1. I am the system administrator (root);
> >> 2. I am using a valid (albeit deprecated from 2.6.31) method to tell
> >> the wireless infrastructure that I want the regulatory domain set to
> >> GB;
> >> 3. GB is a valid code; and
> >> 4. the wireless infrastructure sets the regulatory domain to CN.
> >> 5. in 2.6.30, the wireless infrastructure does what I (the root user)
> >> tell it to do.
> >>
> >> That's a regression in my book. Oh well! I do have the iw and crda
> >> applications installed, so I've taken that route of setting the
> >> regulatory domain to GB.
> >
> > Are you actually getting the wrong regulatory rules enforced? Or are
> > you merely bothered that it is reporting "CN" instead of "GB"?
> >
>
> I'm not sure whether it's wrong or not. To these dmesg snippets from
> my original post look wrong because one of the frequency ranges listed
> for CN is outside those listed for GB and one of the CN max_eirp
> entries is not preent in the GB list. Whether that is OK or not I
> don't know and can't find (lay user) documentation to tell me.
>
> cfg80211: Regulatory domain changed to country: GB
> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
> (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
> (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
> (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
>
> cfg80211: Regulatory domain changed to country: CN
> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
> (5735000 KHz - 5835000 KHz @ 40000 KHz), (N/A, 3000 mBm)
It looks like a mismatch to me. Luis, can you sort this out?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-08-07 15:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 10:50 ath5k - strange regulatory domain change Chris Clayton
2009-08-07 11:24 ` Frans Pop
2009-08-07 12:56 ` Chris Clayton
2009-08-07 13:48 ` John W. Linville
2009-08-07 14:57 ` Chris Clayton
2009-08-07 15:16 ` John W. Linville [this message]
2009-08-07 17:13 ` Luis R. Rodriguez
2009-08-07 17:39 ` Frans Pop
2009-08-07 17:51 ` Luis R. Rodriguez
2009-08-07 18:00 ` John W. Linville
2009-08-07 15:35 ` Frans Pop
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=20090807151304.GE7545@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=chris2553@googlemail.com \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.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).