From: Joerg Pommnitz <pommnitz@yahoo.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: AW: Drivers that do not honor regulatory restrictions
Date: Mon, 4 Jun 2007 05:03:57 -0700 (PDT) [thread overview]
Message-ID: <297494.10588.qm@web51404.mail.re2.yahoo.com> (raw)
Johannes Berg wrote:
> No, that would've been the driver, the firmware has nothing to do with
> the radio frequency at all.
>
> johannes
Actually it was mac80211. In ieee80211_ioctl.c the allowed frequencies for Japan are defined this way:
1574 static const struct ieee80211_channel_range ieee80211_mkk_channels[] = {
1575 { 2412, 2472, 20, 6 } /* IEEE 802.11b/g, channels 1..13 */,
1576 { 5170, 5240, 20, 6 } /* IEEE 802.11a, channels 34..48 */,
1577 { 5260, 5320, 20, 6 } /* IEEE 802.11a, channels 52..64 */,
1578 { 0 }
1579 };
This prevents channel 14 from being used. Changing line 1575 to
1575 { 2412, 2484, 20, 6 } /* IEEE 802.11b/g, channels 1..13 */,
did the trick.
BTW: ieee80211_ioctl_set_regulatory_domain changes conf->regulatory_domain, but this seems not to change the selected frequency table (that one is selected solely based on the module parameter "ieee80211_regdom". Why are there two places to store the regdomain (that seem to be used from different places)?
--
Regards
Joerg
__________________________________ Yahoo! Clever - Der einfachste Weg, Fragen zu stellen und Wissenswertes mit Anderen zu teilen. www.yahoo.de/clever
next reply other threads:[~2007-06-04 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 12:03 Joerg Pommnitz [this message]
2007-06-04 12:06 ` AW: Drivers that do not honor regulatory restrictions Johannes Berg
2007-06-04 12:28 ` Holger Schurig
2007-06-04 20:30 ` 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=297494.10588.qm@web51404.mail.re2.yahoo.com \
--to=pommnitz@yahoo.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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