From: Tony Vroon <tony@linx.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
reinette chatre <reinette.chatre@intel.com>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges
Date: Mon, 16 Feb 2009 12:08:44 +0000 [thread overview]
Message-ID: <1234786124.4271.2.camel@localhost> (raw)
In-Reply-To: <20090214045232.GA5769@tesla>
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
Just to confirm, if I use my early-boot hook that I used for your iw
list to set the regulatory domain manually (iw reg set GB) all is well.
If I allow the driver stack to get to the association stage without
setting a regulatory domain, I can never get my 802.11A spectrum back
after the fact.
Would you still see this as a bug or rather a specific requirement of
the new interface that hasn't yet been documented?
Regards,
Tony V.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-16 12:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 18:09 IWL5300, 2.6.29-rc4, CRDA 1.0.1: Missing out 802.11A frequency ranges Tony Vroon
2009-02-09 18:20 ` Luis R. Rodriguez
2009-02-09 18:22 ` Luis R. Rodriguez
2009-02-09 18:23 ` Tony Vroon
2009-02-09 18:39 ` John W. Linville
2009-02-09 19:21 ` Tony Vroon
2009-02-09 19:35 ` Tony Vroon
2009-02-10 1:39 ` Luis R. Rodriguez
2009-02-10 1:51 ` Tony Vroon
2009-02-10 2:07 ` Luis R. Rodriguez
2009-02-11 19:19 ` Tony Vroon
2009-02-11 21:46 ` Luis R. Rodriguez
2009-02-13 10:55 ` Tony Vroon
2009-02-14 4:52 ` Luis R. Rodriguez
2009-02-14 5:02 ` Luis R. Rodriguez
2009-02-16 12:08 ` Tony Vroon [this message]
2009-02-16 15:47 ` John W. Linville
2009-02-17 18:42 ` Luis R. Rodriguez
2009-02-17 19:06 ` Luis R. Rodriguez
2009-02-20 6: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=1234786124.4271.2.camel@localhost \
--to=tony@linx.net \
--cc=Luis.Rodriguez@Atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=reinette.chatre@intel.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).