From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] New radio fails to init in ath9k_hw_wait Where to add a new reg value type?
Date: Mon, 18 Jul 2011 18:10:44 +0200 [thread overview]
Message-ID: <4E245B04.5080704@openwrt.org> (raw)
In-Reply-To: <CAA9gSzGzHSjEYh6GqeN3e3AurCxHGF4ortxEjf+rg_WY7ktyiA@mail.gmail.com>
On 2011-07-18 6:02 PM, Kelly Hogan wrote:
> Thanks for the response!
>
> This is a 9285 and similar to the UBNT Bullet M radio I believe.
>
> root at OpenWrt:/# dmesg | grep phy
> Determined physical RAM map:
> ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
> Registered led device: ath9k-phy0
> ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xb0000000, irq=72
> root at OpenWrt:/# dmesg | grep ath
> \ath: EEPROM regdomain: 0x0
> ath: EEPROM indicates default country code should be used
> ath: doing EEPROM country->regdmn map search
> ath: country maps to regdmn code: 0x3a
> ath: Country alpha2 being used: US
> ath: Regpair used: 0x3a
> Registered led device: ath9k-phy0
>
> root at OpenWrt:/sys/kernel/debug/ieee80211/phy0/ath9k# cat rx_chainmask
> 0x00000003
> root at OpenWrt:/sys/kernel/debug/ieee80211/phy0/ath9k# cat tx_chainmask
> 0x00000001
I'm pretty sure that explains your problems - the rx chainmask is wrong.
The AR9285 chipset is single-stream and thus cannot have a chainmask of
3 (which would imply dual-stream MIMO Rx).
Try echo 1 > rx_chainmask, and then restart wifi.
If that fixes the issue for you, I'll make a patch to make ath9k
validate the chainmask settings from the EEPROM and fix them if they're
wrong.
- Felix
next prev parent reply other threads:[~2011-07-18 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 22:16 [ath9k-devel] New radio fails to init in ath9k_hw_wait Where to add a new reg value type? Kelly Hogan
2011-07-18 6:40 ` Mohammed Shafi
2011-07-18 15:59 ` Kelly Hogan
2011-07-18 6:40 ` Felix Fietkau
2011-07-18 16:02 ` Kelly Hogan
2011-07-18 16:10 ` Felix Fietkau [this message]
2011-07-19 1:46 ` Outback Dingo
2011-07-19 3:43 ` Adrian Chadd
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=4E245B04.5080704@openwrt.org \
--to=nbd@openwrt.org \
--cc=ath9k-devel@lists.ath9k.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.