From: Holger Schurig <holgerschurig@googlemail.com>
To: Holger Schurig <holgerschurig@googlemail.com>
Cc: Jeffrey Baker <jwbaker@gmail.com>,
linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: Re: Getting random regulatory domains on boot-up with ath9k
Date: Fri, 06 Nov 2009 13:05:52 +0100 [thread overview]
Message-ID: <m3hbt7kgdb.wl%holgerschurig@gmail.com> (raw)
In-Reply-To: <m3ws246ky4.wl%holgerschurig@gmail.com>
Hmm, maybe it's not a bug after all.
The card's eeprom just have a region, 0x37 is ETSI World. Now the
kernel looks for the first country with this region and uses this for
crda.
There have been changes to drivers/net/wireless/ath/regd_common.h
recently, so maybe on one kernel-version "DK" is the first ETSI World,
on the next "AW" is the first and on some other again some different
country.
So it's just misleading, e.g.
using first country with regdm 0x37: DK
would probably a better dmesg output.
If you however can reproduce that with the same kernel you always get
different output after each reboot, then we have a bug here.
next prev parent reply other threads:[~2009-11-06 12:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 8:04 Getting random regulatory domains on boot-up with ath9k Jeffrey Baker
2009-11-06 9:50 ` Holger Schurig
2009-11-06 11:17 ` Davide Pesavento
2009-11-10 10:03 ` Sebastian Kemper
2009-11-10 14:41 ` Luis R. Rodriguez
2009-11-06 12:05 ` Holger Schurig [this message]
2009-11-06 15:53 ` Luis R. Rodriguez
2009-11-06 16:21 ` Luis R. Rodriguez
2009-11-06 16:30 ` Luis R. Rodriguez
2009-11-06 16:44 ` Luis R. Rodriguez
2009-11-07 19:02 ` Jeffrey Baker
2009-11-07 19:42 ` 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=m3hbt7kgdb.wl%holgerschurig@gmail.com \
--to=holgerschurig@googlemail.com \
--cc=jwbaker@gmail.com \
--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).