From: Helmut Schaa <helmut.schaa@googlemail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: reinette chatre <reinette.chatre@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>
Subject: Re: iwl4965: 11a channels disabled in current wireless-testing
Date: Tue, 2 Mar 2010 20:47:09 +0100 [thread overview]
Message-ID: <201003022047.10196.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <43e72e891003011059v564931e2qfe390657b698c277@mail.gmail.com>
Am Montag 01 März 2010 schrieb Luis R. Rodriguez:
> You can try to register to nl80211 events after loading cfg80211:
>
> iw event -t
>
> Then load iwlagn and see if you pick anything up. Might want to enable
> CFG80211_REG_DEBUG.
That's the only regulatory event I get:
1267558985.672513: phy #0: regulatory domain change: set to world roaming by the wireless core upon initialization request
When I set the reg domain to DE via iw I get:
1267559015.166161: regulatory domain change: set to DE by a user request
However all previously disabled channels are still disabled.
Reloading iwlagn afterwards gives the following again:
1267559087.050649: regulatory domain change: set to DE by a user request
And afterwards the 11a channels and 12+13bg are enabled (passive scanning
only, but that is fine) again.
I have no clue what's happening here.
Helmut
next prev parent reply other threads:[~2010-03-02 19:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 14:34 iwl4965: 11a channels disabled in current wireless-testing Helmut Schaa
2010-02-28 22:01 ` [ipw3945-devel] " Rafał Miłecki
2010-02-28 22:02 ` Rafał Miłecki
2010-02-28 22:23 ` Helmut Schaa
2010-03-01 17:46 ` reinette chatre
2010-03-01 18:07 ` Luis R. Rodriguez
2010-03-01 18:27 ` Helmut Schaa
2010-03-01 18:59 ` Luis R. Rodriguez
2010-03-02 19:47 ` Helmut Schaa [this message]
2010-03-03 18:18 ` reinette chatre
2010-03-03 19:08 ` Helmut Schaa
2010-03-03 19:29 ` [ipw3945-devel] " John W. Linville
2010-03-03 20:05 ` Helmut Schaa
2010-03-03 20:14 ` Daniel Halperin
2010-03-03 21:19 ` reinette chatre
2010-03-03 22:54 ` Daniel Halperin
2010-03-04 10:24 ` Daniel Halperin
2010-03-04 17:31 ` Luis R. Rodriguez
2010-03-09 22:05 ` Daniel Halperin
2010-03-09 22:56 ` Daniel Halperin
2010-03-10 6:41 ` reinette chatre
2010-03-13 14:01 ` Helmut Schaa
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=201003022047.10196.helmut.schaa@googlemail.com \
--to=helmut.schaa@googlemail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.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).