Linux wireless drivers development
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: CRDA and ath5k with no country code in EEPROM
Date: Tue, 30 Mar 2010 13:41:35 +0200	[thread overview]
Message-ID: <m3r5n2qbo0.fsf@intrepid.localdomain> (raw)
In-Reply-To: <43e72e891003291500w632cb789r6860dae9ccdf744c@mail.gmail.com> (Luis R. Rodriguez's message of "Mon, 29 Mar 2010 15:00:47 -0700")

"Luis R. Rodriguez" <mcgrof@gmail.com> writes:

>> So what exactly do I change? Can the regulatory.bin change the default
>> country?
>
> Huh?
>
>> Remember I need to be compliant to the US freq sets as well - when the
>> regdomain is set to US. IOW I can't allow the user operating the device
>> to set e.g. channel 12 when the user selects country=US (so there is a
>> big difference between country 0=US and the real country=US).
>
> Huh?

Not sure what do you mean. Are my expectations unrealistic?

>> But the driver says:
>> ath: EEPROM regdomain: 0x0
>> ath: EEPROM indicates default country code should be used
>> ath: doing EEPROM country->regdmn map search
>> ath: country maps to regdmn code: 0x3a
>> ath: Country alpha2 being used: US
>> ath: Regpair used: 0x3a
>>
>> At least for the driver 0 doesn't mean US, it means "default country".
>> Perhaps the meaning of "default country" depends on maybe location of
>> the hw and/or sw manufacturer?
>
> I just pointed to some documentation for you which indicated 0x0 means
> "US".

Yes, but the meaning depends on the POV. What is important to me is what
does that mean to a) the software I use, b) the hardware I use (cards).
The driver doesn't say 0=US, perhaps it should? Then things would be
very different.
-- 
Krzysztof Halasa

  reply	other threads:[~2010-03-30 11:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-28 20:52 CRDA and ath5k with no country code in EEPROM Krzysztof Halasa
2010-03-28 23:45 ` Luis R. Rodriguez
2010-03-29 19:15   ` Krzysztof Halasa
2010-03-29 19:22     ` Luis R. Rodriguez
2010-03-29 19:49       ` Krzysztof Halasa
2010-03-29 19:56         ` Luis R. Rodriguez
2010-03-29 20:48           ` Krzysztof Halasa
2010-03-29 22:00             ` Luis R. Rodriguez
2010-03-30 11:41               ` Krzysztof Halasa [this message]
2010-03-30 16:28                 ` Luis R. Rodriguez
2010-03-30 18:21                   ` Krzysztof Halasa
2010-03-30 18:40                     ` Luis R. Rodriguez
2010-03-30 20:13                       ` Krzysztof Halasa
2010-03-30 18:49                     ` Christian Lamparter
2010-03-30 18:52                       ` Luis R. Rodriguez
2010-03-30 20:33                       ` Krzysztof Halasa
2010-03-30 22:07                         ` Luis R. Rodriguez
2010-03-31  0:26                           ` Krzysztof Halasa
2010-03-30 22:11                         ` Christian Lamparter
2010-03-30  6:42             ` Holger Schurig
2010-03-30 11:46               ` Krzysztof Halasa
2010-03-29 20:04         ` Christian Lamparter
2010-03-29 20:54           ` Krzysztof Halasa
2010-03-29 21:57           ` 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=m3r5n2qbo0.fsf@intrepid.localdomain \
    --to=khc@pm.waw.pl \
    --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