linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 1 Mar 2010 19:27:52 +0100	[thread overview]
Message-ID: <201003011927.53208.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <43e72e891003011007p6053aaaewef3a0d639159c120@mail.gmail.com>

Am Montag 01 März 2010 schrieb Luis R. Rodriguez:
> On Mon, Mar 1, 2010 at 9:46 AM, reinette chatre
> <reinette.chatre@intel.com> wrote:
> > On Sun, 2010-02-28 at 06:34 -0800, Helmut Schaa wrote:
> >> have there been any recent changes to the regulatory stuff, especially
> >> in conjunction with iwlagn?
> >>
> >> Because with wireless-testing I get all 11a channels disabled by default
> >> and the same for channels 12 & 13 in the g-band.
> >
> > This could be related to a change in the default regulatory domain. It
> > used to be US, but now it is world,
> 
> This change actually happened a while ago and the world regulatory
> domain actually enables passive scanning on a lot of channels instead
> of straight out disabling them.

How do channels get disabled then?

> > which is more restrictive. You can
> > modify your regulatory domain using "iw reg set <domain>"
> 
> For Intel, as well as with Atheros cards, cards using 'iw reg set'
> would actually not yield enabling new channels, it would only disable
> channels further.

Right, that's what I can see here as well.

However, I just noticed in dmesg:

iwlagn 0000:10:00.0: Tunable channels: 13 802.11bg, 19 802.11a channels

So it seems the card reports the correct set of channels but it doesn't
get reflected in cfg80211.

Thanks,
Helmut

  reply	other threads:[~2010-03-01 18:27 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 [this message]
2010-03-01 18:59       ` Luis R. Rodriguez
2010-03-02 19:47         ` Helmut Schaa
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=201003011927.53208.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).