linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helmut Schaa <helmut.schaa@googlemail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	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: [ipw3945-devel] iwl4965: 11a channels disabled in current wireless-testing
Date: Wed, 3 Mar 2010 21:05:08 +0100	[thread overview]
Message-ID: <201003032105.08938.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <20100303192946.GC23920@tuxdriver.com>

Am Mittwoch 03 März 2010 schrieb John W. Linville:
> On Wed, Mar 03, 2010 at 08:08:47PM +0100, Helmut Schaa wrote:
> > Am Mittwoch 03 März 2010 schrieb reinette chatre:
> 
> > > $ iw reg get
> > > country 00:
> > > 	(2402 - 2472 @ 40), (3, 20)
> > > 	(2457 - 2482 @ 20), (3, 20), PASSIVE-SCAN, NO-IBSS
> > > 	(2474 - 2494 @ 20), (3, 20), NO-OFDM, PASSIVE-SCAN, NO-IBSS
> > > 	(5170 - 5250 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS
> > > 	(5735 - 5835 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS
> > 
> > Oops, that's what I get:
> > 
> > country 00:
> >         (2402 - 2472 @ 40), (3, 20)
> > 
> > Luis, is the world reg domain encoded in cfg80211 or in the regdb? Maybe
> > the regdb is too old or something like that?
> 
> Should be both -- start w/ the one encoded in the kernel and request
> an update from userland if it is available.
> 
> Hth!

It does indeed. I moved crda out of the way so that it cannot get called
anymore and after loading cfg80211, mac80211 and iwlagn I had all the
channels set up the same way as Reinette (and that is how I expected it to
be).

So I guess it's my regdb that's outdated.

Thanks,
Helmut

  reply	other threads:[~2010-03-03 20:05 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
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 [this message]
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=201003032105.08938.helmut.schaa@googlemail.com \
    --to=helmut.schaa@googlemail.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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).