From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: Krzysztof Halasa <khc@pm.waw.pl>, linux-wireless@vger.kernel.org
Subject: Re: CRDA and ath5k with no country code in EEPROM
Date: Tue, 30 Mar 2010 11:52:19 -0700 [thread overview]
Message-ID: <43e72e891003301152l1b0c4c02n706545d51b8d44c9@mail.gmail.com> (raw)
In-Reply-To: <201003302049.24231.chunkeey@googlemail.com>
On Tue, Mar 30, 2010 at 11:49 AM, Christian Lamparter
<chunkeey@googlemail.com> wrote:
> On Tuesday 30 March 2010 20:21:36 Krzysztof Halasa wrote:
>> "Luis R. Rodriguez" <mcgrof@gmail.com> writes:
>>
>> > My point was that this is not something meant to be interpreted by
>> > anyone for what "default country" means, the documentation I pointed
>> > out clearly states that 0x0 is designed to mean to match the "US" by
>> > Atheros hardware as per hardware documentation provided to ODMs.
>>
>> I understand this, but the reality is that I have to work with hardware
>> and software, not with the docs provided by Atheros to some other
>> parties.
>>
>> Software (the official Atheros driver, to be precise) says 0 isn't
>> exactly US.
>> Hardware (card) manufacturer says 0 isn't US.
>
> Are you sure, you (or the hw manufacturer for that matter) didn't confuse
> the country code with regdomain code?
>
> because while they have more or less the same function, they do have different
> mappings. The 0x00 country code is reserved for the FCC (US), while the 0x00
> regdomain code is a described as "debug" with supposedly no limitations?!
That debug regulatory domain is not a valid regulatory domain
supported in the field, it was a debug hack. It is simply not a
regulatory domain which ODMs / OEMs calibrate their cards for.
Luis
next prev parent reply other threads:[~2010-03-30 18:52 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
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 [this message]
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=43e72e891003301152l1b0c4c02n706545d51b8d44c9@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=chunkeey@googlemail.com \
--cc=khc@pm.waw.pl \
--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).