From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k regulatory
Date: Mon, 26 Jan 2009 07:13:02 -0800 [thread overview]
Message-ID: <20090126151302.GL22475@tesla> (raw)
In-Reply-To: <5b7270f40901260535q382f98d3qa6549556332b8d91@mail.gmail.com>
On Mon, Jan 26, 2009 at 05:35:13AM -0800, Zoltan Devai wrote:
> Hi,
>
> I'm using a TP-Link TL-WN861N card. What could be the reason that channels 12 and 13 are
> not allowed ?
> Using compat-wireless 2009-01-25.
> Relevant dmesg output:
>
> cfg80211: Using static regulatory domain info
> cfg80211: Regulatory domain: US
> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
> (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
> (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
> cfg80211: Calling CRDA for country: DE
> cfg80211: Regulatory domain changed to country: DE
> (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm)
> (5150000 KHz - 5255000 KHz @ 40000 KHz), (N/A, 2301 mBm)
> (5470000 KHz - 5650000 KHz @ 40000 KHz), (N/A, 3000 mBm)
> ath9k: 0.1
> PCI: enabling device 0000:00:02.0 (0140 -> 0142)
> ath9k: 2MHz channel: 2412, channelFlags: 0x300e0
> ath9k: 2MHz channel: 2417, channelFlags: 0x300e0
> ath9k: 2MHz channel: 2422, channelFlags: 0x300e0
> ath9k: 2MHz channel: 2427, channelFlags: 0x300e0
> ath9k: 2MHz channel: 2432, channelFlags: 0x700e0
> ath9k: 2MHz channel: 2437, channelFlags: 0x700e0
> ath9k: 2MHz channel: 2442, channelFlags: 0x700e0
> ath9k: 2MHz channel: 2447, channelFlags: 0x500e0
> ath9k: 2MHz channel: 2452, channelFlags: 0x500e0
> ath9k: 2MHz channel: 2457, channelFlags: 0x500e0
> ath9k: 2MHz channel: 2462, channelFlags: 0x500e0
> ath9k: Rate: 1Mbps, ratecode: 27
> ath9k: Rate: 2Mbps, ratecode: 26
> ath9k: Rate: 5Mbps, ratecode: 25
> ath9k: Rate: 11Mbps, ratecode: 24
> ath9k: Rate: 6Mbps, ratecode: 11
> ath9k: Rate: 9Mbps, ratecode: 15
> ath9k: Rate: 12Mbps, ratecode: 10
> ath9k: Rate: 18Mbps, ratecode: 14
> ath9k: Rate: 24Mbps, ratecode: 9
> ath9k: Rate: 36Mbps, ratecode: 13
> ath9k: Rate: 48Mbps, ratecode: 8
> ath9k: Rate: 54Mbps, ratecode: 12
> ath9k: Rate: 6Mbps, ratecode: 11
> ath9k: Rate: 9Mbps, ratecode: 15
> ath9k: Rate: 12Mbps, ratecode: 10
> ath9k: Rate: 18Mbps, ratecode: 14
> ath9k: Rate: 24Mbps, ratecode: 9
> ath9k: Rate: 36Mbps, ratecode: 13
> ath9k: Rate: 48Mbps, ratecode: 8
> ath9k: Rate: 54Mbps, ratecode: 12
> ath9k: tx DMA: 512 buffers 1 desc/buf
> ath9k: tx DMA map: ffc08000 (73728) -> 1f80000 (73728)
> ath9k: beacon DMA: 1 buffers 1 desc/buf
> ath9k: beacon DMA map: ffc1a000 (144) -> 1eb3000 (144)
> ath9k: cachelsz 32 rxbufsize 3872
> ath9k: rx DMA: 512 buffers 1 desc/buf
> ath9k: rx DMA map: ffc1b000 (73728) -> 1fa0000 (73728)
> phy0: Selected rate control algorithm 'ath9k_rate_control'
> Registered led device: ath9k-phy0:radio
> Registered led device: ath9k-phy0:assoc
> Registered led device: ath9k-phy0:tx
> Registered led device: ath9k-phy0:rx
> phy0: Atheros AR5416 MAC/BB Rev:2 AR2122 RF Rev:81: mem=0xc2900000, irq=27
I take it the second DE regulatory request was yours? Anyway -- since
I am not seeing any print out during ath9k's initialization on regulatory
it would seem your card uses one of the built-in regulatory domains.
You can use iw to see your allowed channels:
iw list
If your regulatory domain does not allow for it you will not be able to use that
channel.
To confirm you can recompile ath9k with debugging enabled with the patch
attached applied. Then load ath9k as follows:
insmod drivers/net/wireless/ath9k/ath9k.ko debug=0x00000080
0x00000080 is ATH_DBG_REGULATORY so this will show all regulatory debug prints.
Luis
From: Luis R. Rodriguez <lrodriguez@atheros.com>
Date: Mon, 26 Jan 2009 06:41:48 -0800
Subject: [PATCH] ath9k: fix debug print on regd
With debugging enabled and with ATH_DBG_REGULATORY
selected we wouldn't get the full print out of one line,
reason is we used "," instead of nothing to separate two
lines.
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
---
drivers/net/wireless/ath9k/regd.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/wireless/ath9k/regd.c b/drivers/net/wireless/ath9k/regd.c
index 90f0c98..ec88f78 100644
--- a/drivers/net/wireless/ath9k/regd.c
+++ b/drivers/net/wireless/ath9k/regd.c
@@ -447,7 +447,7 @@ int ath9k_regd_init(struct ath_hal *ah)
}
DPRINTF(ah->ah_sc, ATH_DBG_REGULATORY,
- "Country alpha2 being used: %c%c\n",
+ "Country alpha2 being used: %c%c\n"
"Regpair detected: 0x%0x\n",
ah->alpha2[0], ah->alpha2[1],
ah->regpair->regDmnEnum);
--
1.5.6.4
next prev parent reply other threads:[~2009-01-26 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 13:35 [ath9k-devel] ath9k regulatory Zoltan Devai
2009-01-26 15:13 ` Luis R. Rodriguez [this message]
2009-01-26 15:15 ` Luis R. Rodriguez
2009-01-26 18:08 ` Zoltan Devai
2009-01-26 18:38 ` Luis R. Rodriguez
2009-01-26 23:37 ` Zoltan Devai
2009-01-26 23:53 ` Luis R. Rodriguez
-- strict thread matches above, loose matches on Subject: below --
2009-01-27 2:20 Lars Hardy
2009-01-27 2: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=20090126151302.GL22475@tesla \
--to=lrodriguez@atheros.com \
--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.