From: Helmut Schaa <helmut.schaa@googlemail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org, ipw3945-devel@lists.sourceforge.net
Subject: Re: [ipw3945-devel] iwl4965: 11a channels disabled in current wireless-testing
Date: Sun, 28 Feb 2010 23:23:02 +0100 [thread overview]
Message-ID: <201002282323.02489.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <b170af451002281402w2ffd2f29t70e4dedf216b21fc@mail.gmail.com>
Am Sonntag 28 Februar 2010 schrieb Rafał Miłecki:
> W dniu 28 lutego 2010 23:01 użytkownik Rafał Miłecki <zajec5@gmail.com> napisał:
> > 2010/2/28 Helmut Schaa <helmut.schaa@googlemail.com>:
> >> 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.
> >
> > Please google for regulatory and regions. Higher frequencies
> > (channels) are not allowed in some countries.
>
> Blah, you wrote about regulatory changes... Ignore my response.
Yeah, maybe I wasn't precise enough. I always had quite a number of 11a
channels enabled with my iwl4965 (AFAIK depending on the channel mask encoded
in the cards EEPROM) but that changed some time ago. I don't know when because
I didn't have a need to connect to 11a APs for quite some time. Hence my
question.
Helmut
next prev parent reply other threads:[~2010-02-28 22:23 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 [this message]
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
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=201002282323.02489.helmut.schaa@googlemail.com \
--to=helmut.schaa@googlemail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.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).