linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Holger Schurig <holgerschurig@googlemail.com>
To: Jeffrey Baker <jwbaker@gmail.com>
Cc: 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 10:50:43 +0100	[thread overview]
Message-ID: <m3ws246ky4.wl%holgerschurig@gmail.com> (raw)
In-Reply-To: <fd145f7d0911060004j55b06482tca088685d0626249@mail.gmail.com>

> ath: EEPROM regdomain: 0x37
> ath: EEPROM indicates we should expect a direct regpair map
> ath: Country alpha2 being used: AW
> ath: Regpair used: 0x37
> cfg80211: Calling CRDA for country: AW

I can confirm this bug on wireless-testing, v2.6.32-rc6-41576-g4408b3b
with an ath5k card:

[    9.193118] ath: doing EEPROM country->regdmn map search
[    9.193121] ath: country maps to regdmn code: 0x37
[    9.193124] ath: Country alpha2 being used: DK
[    9.193126] ath: Regpair used: 0x37
[    9.207182] phy0: Selected rate control algorithm 'minstrel'
[    9.207874] ath5k phy0: Atheros AR2414 chip found (MAC: 0x79, PHY: 0x45)
[    9.208801] cfg80211: Calling CRDA for country: DK
[    9.221773] cfg80211: Regulatory domain changed to country: DK

  reply	other threads:[~2009-11-06  9:50 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 [this message]
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
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=m3ws246ky4.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).