From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Joerg Albert <jal2@gmx.de>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Christian Lamparter <chunkeey@web.de>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
<Stephen.Chen@atheros.com>
Subject: Re: ath/regd.c: regdomain 0x8000 fails to retrieve a regulatory domain pair
Date: Mon, 11 May 2009 12:06:02 -0700 [thread overview]
Message-ID: <20090511190602.GC18696@tesla> (raw)
In-Reply-To: <4A0802B0.9070206@gmx.de>
On Mon, May 11, 2009 at 03:49:20AM -0700, Joerg Albert wrote:
> Plugging in a WNDA3100 (ar9170usb) I get the error
>
> ath: No regulatory domain pair found, cannot continue
>
> Seems like the EEPROM of the stick initializes regulatory.current_rd
> to 0x8000, current_rd_ext to 0. Is this a valid setting?
>
> Looked into ath/regd.c, ath_regd_init():
>
> ath_get_regpair(regdmn)
>
> is called with regdmn == 0x8000 and returns NULL.
>
> Shall that regdmn value be dealt with by
>
> if (reg->country_code == CTRY_DEFAULT &&
> regdmn == CTRY_DEFAULT)
> reg->country_code = CTRY_UNITED_STATES;
> ?
>
> wireless-testing is git v2.6.30-rc4-22735-gbd48c47, I run
> compat-wireless with a 2.6.29.2 kernel.
Thanks for reporting this.
Stephen do ar9170 cards get sold with a regulatory domain set to 0x8000?
If so we need to deal with this in the common ath.ko module and set the regulatory
domain as intended.
If we are not sure we can simply default to one of the world regulatory domains for
this specific case, 0x64, for example.
Thanks,
Luis
next prev parent reply other threads:[~2009-05-11 19:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 10:49 ath/regd.c: regdomain 0x8000 fails to retrieve a regulatory domain pair Joerg Albert
2009-05-11 19:06 ` Luis R. Rodriguez [this message]
[not found] ` <618D4DE9D5223A45A46C48063FD640451098774889@TAEXMB-01.global.atheros.com>
2009-05-21 17:16 ` Luis R. Rodriguez
2009-05-21 18:19 ` Gábor Stefanik
2009-05-21 19:03 ` Luis R. Rodriguez
2009-05-21 23:22 ` Joerg Albert
2009-05-21 23:57 ` Luis R. Rodriguez
2009-05-22 0:11 ` Luis R. Rodriguez
2009-05-22 13:12 ` Joerg Albert
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=20090511190602.GC18696@tesla \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=Stephen.Chen@atheros.com \
--cc=chunkeey@web.de \
--cc=jal2@gmx.de \
--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).