From: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "ath5k-devel@lists.ath5k.org" <ath5k-devel@lists.ath5k.org>
Subject: Re: regulatory problems with ath5k
Date: Wed, 26 May 2010 19:07:40 +0200 [thread overview]
Message-ID: <4BFD555C.4060205@nets.rwth-aachen.de> (raw)
In-Reply-To: <4BFD04A4.4000403@nets.rwth-aachen.de>
Hi,
FWI: I believe this whole regulatory framework is pretty broken in 2.6.34
If I associate with a 802.11g accesspoint with one NIC , I'm not allowed
to use 802.11a on my other NIC at all.
[ 23.352168] wlan0: associated
[ 23.355993] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 23.375106] cfg80211: Calling CRDA for country: DE
[ 23.412542] cfg80211: Current regulatory domain updated by AP to: DE
[ 23.431728] (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 23.454319] (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 1800 mBm)
# iw reg get
country 98:
(2402 - 2482 @ 40), (N/A, 18)
???
Best regards,
Arnd
next prev parent reply other threads:[~2010-05-26 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 11:23 regulatory problems with ath5k Arnd Hannemann
2010-05-26 17:07 ` Arnd Hannemann [this message]
2010-05-26 17:45 ` Luis R. Rodriguez
2010-05-26 17:11 ` Luis R. Rodriguez
2010-05-26 18:09 ` Arnd Hannemann
2010-05-26 18:12 ` 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=4BFD555C.4060205@nets.rwth-aachen.de \
--to=hannemann@nets.rwth-aachen.de \
--cc=ath5k-devel@lists.ath5k.org \
--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 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).