From: Brian Morrison <bdm@fenrir.org.uk>
To: linux-wireless@vger.kernel.org
Subject: Re: [ipw3945-devel] iwl3945: Disabled channels
Date: Mon, 21 Apr 2008 15:19:12 +0100 [thread overview]
Message-ID: <480CA260.70506@fenrir.org.uk> (raw)
In-Reply-To: <1208785818.26186.101.camel@johannes.berg>
Johannes Berg wrote:
>> If you're in the EU, I contributed a fix that has not yet made it into
>> the iwlwifi code as it is under review (the whole regulatory aspect is
>> difficult, there are so many caveats!).
>
> Technically, it's cfg80211 code; the reason that it's not in yet is that
> I'm unsure about the legal situation of the ETSI and the national
> bodies, it seems to me that the ultimate decision is done by the
> national bodies and last I heard France had quite different restrictions
> than Germany, for example.
OK, sorry about the naming mixup, you are, of course, correct. I have
not really got to grips with how all these different sub-systems fit
together. I also see that the mac80211 and cfg80211 changes that are in
Fedora have not made it into mainline 2.6.25, so I assume it will go
into 2.6.26?
>
> Does anyone have that info? I can dig up the info for Germany easily
> (the "Frequenznutzungsplan" is available on the regulatory agency web
> site as pdf)
Here is a link that came from the Wikipedia page I mentioned in my post:
http://www.arcep.fr/index.php?id=8571&L=1&tx_gsactualite_pi1%5Buid%5D=232&tx_gsactualite_pi1%5Bannee%5D=2003&tx_gsactualite_pi1%5Btheme%5D=0&tx_gsactualite_pi1%5Bmotscle%5D=&tx_gsactualite_pi1%5BbackID%5D=2122&cHash=a558568045
This document applies to the list of 58 departements shown. It says that
with these departments all channels may be used indoors at +20dBm
(100mW). Outdoors +10dBm (10mW) is allowed on all channels but below
2454MHz +20dBm (100mW) is allowed. Another quick check shows that there
are 100 departements in France. Also note that this dates from 2002 and
states that new lists of departements will be published in 2003 and
2004, so presumably the number of departements will have increased by now.
I can't imagine how this regulatory mess is enforceable or how any other
OS/hardware combination does it. I'll have to say that I work for a
company that produces Wi-Fi chips and products based on them and that we
find the whole regulatory situation worldwide just as confusing as
everyone else does.
A complete country/regulatory map is going to be very difficult to
research and implement, I assume that we can't go far wrong if we used
something like the Intel EEPROM contents as a guide to what can be done?
I assume that local infrastructure will comply with local restrictions,
so it's mainly IBSS use that needs controlling. And power output, which
could be difficult if we need to know whether we're outdoors or not.
Comments folks?
--
Brian
next prev parent reply other threads:[~2008-04-21 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fuhkfp$mnk$1@ger.gmane.org>
2008-04-21 9:14 ` [ipw3945-devel] iwl3945: Disabled channels Brian Morrison
2008-04-21 13:50 ` Johannes Berg
2008-04-21 14:19 ` Brian Morrison [this message]
2008-04-21 14:41 ` Johannes Berg
2008-04-21 15:01 ` Brian Morrison
2008-04-21 15:12 ` Johannes Berg
2008-04-21 15:36 ` Brian Morrison
2008-04-21 14:28 ` Brian Morrison
2008-04-21 15:38 ` Thomas Bächler
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=480CA260.70506@fenrir.org.uk \
--to=bdm@fenrir.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).