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: Mon, 29 Mar 2010 22:48:18 +0200 [thread overview]
Message-ID: <m3y6hayhv1.fsf@intrepid.localdomain> (raw)
In-Reply-To: <43e72e891003291256t7f53dcfck5f8c8cf94128eeb3@mail.gmail.com> (Luis R. Rodriguez's message of "Mon, 29 Mar 2010 12:56:50 -0700")
"Luis R. Rodriguez" <mcgrof@gmail.com> writes:
>> But... isn't the modifying of the regulatory.bin (the US part of it)
>> to include channels valid in e.g. Europe breaking the (US) rules?
>
> Not if you sign off on it, which is exactly why the whole singing
> thing was invented. You would do this if say, you sell an AP and you
> verify and tested regulatory compliance against a different regulatory
> region.
So what exactly do I change? Can the regulatory.bin change the default
country?
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).
> country code programmed to 0 is defined by Atheros documentation to be
> in the "US".
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?
Then maybe what I really need to do is substituting "EU" as the default
country and enforcing EU restrictions, even when the country selected by
the user is outside EU (e.g. enforcing EU+US in US)?
And when the user gets a card with country=US (not 0), the EU
restictions would be dropped (when physically in USA)?
I think this all reduces to the meaning of country=0 for cards sold (in
this case) in Europe (and maybe manufactured here).
If the driver said "EEPROM regdomain: 0x0 = US" I'd return the cards to
the manufacturer, simple (realistically they'd fix the EEPROM instead).
--
Krzysztof Halasa
next prev parent reply other threads:[~2010-03-29 20:48 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 [this message]
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
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=m3y6hayhv1.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;
as well as URLs for NNTP newsgroup(s).