linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Clayton <chris2553@googlemail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Frans Pop <elendil@planet.nl>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ath5k - strange regulatory domain change
Date: Fri, 7 Aug 2009 15:57:30 +0100	[thread overview]
Message-ID: <c6b1100b0908070757t7b973180s17959e0f46347d5d@mail.gmail.com> (raw)
In-Reply-To: <20090807134803.GA7545@tuxdriver.com>

Hi John,

2009/8/7 John W. Linville <linville@tuxdriver.com>:
> On Fri, Aug 07, 2009 at 01:56:43PM +0100, Chris Clayton wrote:
>> Thanks Frans,
>>
>> 2009/8/7 Frans Pop <elendil@planet.nl>:
>> > Chris Clayton wrote:
>> >> Because of some problems with my Belkin Wireless G card  (model
>> >> F5D7010) and the rt61pci driver, I've started to use a "no-name" card
>> >> that is supported by the ath5k driver.
>> >>
>> >> A problem is that I have come across is that for some reason the CN
>> >> regulatory domain is being set automatically. This doesn't happen with
>> >> the Belkin (rt61) card. I have the following line in
>> >> /etc/modprobe.d/modprobe.conf to set the regulatory domain to GB:
>> >>
>> >> options cfg80211 ieee80211_regdom=GB
>> >
>> > This issue has already been discussed extensively (after I reported it).
>> > Please see the following thread: http://lkml.org/lkml/2009/7/8/421. It
>> > contains a lot of information from the wireless maintainers.
>> >
>>
>> 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)


Thanks

Chris

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



-- 
No, Sir; there is nothing which has yet been contrived by man, by which
so much happiness is produced as by a good tavern or inn - Doctor Samuel
Johnson

  reply	other threads:[~2009-08-07 14:57 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 [this message]
2009-08-07 15:16         ` John W. Linville
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=c6b1100b0908070757t7b973180s17959e0f46347d5d@mail.gmail.com \
    --to=chris2553@googlemail.com \
    --cc=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --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).