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 20:21:36 +0200 [thread overview]
Message-ID: <m3wrwtoekv.fsf@intrepid.localdomain> (raw)
In-Reply-To: <43e72e891003300928qdd70de4vc7585d7e19d36dca@mail.gmail.com> (Luis R. Rodriguez's message of "Tue, 30 Mar 2010 09:28:28 -0700")
"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.
What do you think can I do?
I obviously would go the regulatory.bin way, if it was possible. But
I think regulatory.bin simply describes frequencies etc. valid in
different countries, and if the file contains correct data (and it seems
it does), there is nothing I can "fix" there.
For now I think the best I can do is to add
CONFIG_*80211_DEFAULT_COUNTRY (with default = "US"), and to treat 0 as
this DEFAULT_COUNTRY. This way I don't enable users to disobey the rules
(more than they're already able, since they can patch and recompile
anyway), and at the same time I don't put the (inappropriate for many
people) default country in the sources.
--
Krzysztof Halasa
next prev parent reply other threads:[~2010-03-30 18:21 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 [this message]
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=m3wrwtoekv.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).