From: Joerg Albert <jal2@gmx.de>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Stephen Chen <Stephen.Chen@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Christian Lamparter <chunkeey@web.de>
Subject: Re: ath/regd.c: regdomain 0x8000 fails to retrieve a regulatory domain pair
Date: Fri, 22 May 2009 01:22:01 +0200 [thread overview]
Message-ID: <4A15E219.7040908@gmx.de> (raw)
In-Reply-To: <20090521171619.GB28691@tesla>
On 05/21/2009 07:16 PM, Luis R. Rodriguez wrote:
> Joerg, can you please try this patch, its just informative and I would
> like to see the output. A regulatory domain in the EEPROM set to 0x8000
> should be cought, as you indicated, in this code:
>
> if (reg->country_code == CTRY_DEFAULT &&
> regdmn == CTRY_DEFAULT)
> reg->country_code = CTRY_UNITED_STATES;
>
> The debug prints should help.
> ...
With the patch I get:
usb 1-5: firmware: requesting ar9170-2.fw
ath: EEPROM indicates we should expect a country code
ath: No regulatory domain pair found, cannot continue
ar9170usb: probe of 1-5:1.0 failed with error -22
IMHO the in the above if-statement regdmn == 0x8000 (as read from
the EEPROM by ath_regd_get_eepromRD), but CTRY_DEFAULT is defined as
zero, so reg->country_code isn't set.
Shouldn't we say "regdmn == (CTRY_DEFAULT|COUNTRY_ERD_FLAG)",because
without the ERD flag set we cannot compare a regdomain with a
country code?
/Joerg
next prev parent reply other threads:[~2009-05-21 23:22 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
[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 [this message]
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=4A15E219.7040908@gmx.de \
--to=jal2@gmx.de \
--cc=Stephen.Chen@Atheros.com \
--cc=chunkeey@web.de \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.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).