From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: erwin.vandevelde@gmail.com, linux-wireless@vger.kernel.org
Subject: Re: ath9k bug in country domain handling
Date: Sun, 17 Jun 2012 20:16:21 +0200 [thread overview]
Message-ID: <4FDE1EF5.9030805@gmail.com> (raw)
Erwin Van de Velde wrote:
> I have 802.11n cards with an atheros chipset with no default country domain.
> Upon initialization, crda is set to US domain, after which I try to change it
> to another domain, the driver only accepts further limitations: i.e. if a
> channel is allowed in the US but not in Belgium, it is disabled, but the other
> way round: if a channel is not allowed in the US, but is allowed in Belgium it
> is not enabled.
"no default country domain" :-???
# dmesg | grep ath:
look for:
ath: EEPROM regdomain: XXX
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: XX
ath: Regpair used: XXX
This is a Atheros *driver* feature.
Channels are restricted based on the EEPROM value.
And crda/wireless-regdb only can makes things _worse_.
Solutions:
- modify the driver
- reprogramming of the EEPROM
- buy another board and keep away from Atheros chipsets
You should read:
http://wireless.kernel.org/en/users/Drivers/ath#Regulatory
http://marc.info/?l=linux-wireless&m=125072768530674
http://marc.info/?l=linux-wireless&m=125078520924477
http://wiki.openwrt.org/doc/howto/wireless.utilities?s[]=regulatory#iw see "Note:"
In linux source code, see regd* files:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree;f=drivers/net/wireless/ath
next reply other threads:[~2012-06-17 18:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 18:16 Xose Vazquez Perez [this message]
2012-06-18 12:25 ` ath9k bug in country domain handling Erwin Van de Velde
2012-06-18 22:31 ` Xose Vazquez Perez
2012-06-18 23:46 ` Julian Calaby
2012-06-20 22:30 ` Xose Vazquez Perez
2012-06-21 0:23 ` Julian Calaby
-- strict thread matches above, loose matches on Subject: below --
2012-06-13 11:17 Erwin Van de Velde
2012-06-15 19:00 ` Schrober
2012-06-15 21:51 ` Erwin Van de Velde
2012-06-17 2:15 ` Julian Calaby
2012-06-17 17:12 ` Erwin Van de Velde
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=4FDE1EF5.9030805@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=erwin.vandevelde@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.