From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: linux-wireless@vger.kernel.org
Subject: Re: CRDA and ath5k with no country code in EEPROM
Date: Sun, 28 Mar 2010 16:45:59 -0700 [thread overview]
Message-ID: <43e72e891003281645m1da47a1en882df4432733977d@mail.gmail.com> (raw)
In-Reply-To: <m3tys0tbhk.fsf@intrepid.localdomain>
On Sun, Mar 28, 2010 at 1:52 PM, Krzysztof Halasa <khc@pm.waw.pl> wrote:
> Hi,
>
> I'm not sure I get it right:
> I have an ath5k card without a country code in EEPROM. I think such card
> is supposed to not force any additional restrictions, am I wrong?
> The problem is "no country code" is effectively equal to US, i.e. it's
> forcing additional US restrictions no matter what the actual regdomain
> is.
>
> Linux 2.6.33.
>
> ath5k 0000:00:0d.0: registered as 'phy0'
> ath: EEPROM regdomain: 0x0
I've documented this specific case here:
http://wireless.kernel.org/en/users/Drivers/ath/#The_0x0_regulatory_domain
Luis
next prev parent reply other threads:[~2010-03-28 23:46 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 [this message]
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
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=43e72e891003281645m1da47a1en882df4432733977d@mail.gmail.com \
--to=mcgrof@gmail.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).