From: Brian Morrison <bdm@fenrir.org.uk>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] cfg80211: add EU regulatory domain
Date: Mon, 31 Mar 2008 23:00:30 +0100 [thread overview]
Message-ID: <20080331230030.18da1c21@peterson.fenrir.org.uk> (raw)
In-Reply-To: <1206997315-15878-1-git-send-email-linville@tuxdriver.com>
On Mon, 31 Mar 2008 17:01:55 -0400
"John W. Linville" <linville@tuxdriver.com> wrote:
> Based on initial footwork from Brian Morrison.
>
> Cc: Brian Morrison <bdm@fenrir.org.uk>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
> ---
> Is this worth having? I'm surprised no one has asked for it until
> recently...
>
> Are these values correct? Including the power and gain values? Does
> anyone know have a link to an authoritative source?
>
> net/wireless/reg.c | 16 ++++++++++++++++
> 1 files changed, 16 insertions(+), 0 deletions(-)
>
> diff --git a/net/wireless/reg.c b/net/wireless/reg.c
> index 8cc6037..998ceb6 100644
> --- a/net/wireless/reg.c
> +++ b/net/wireless/reg.c
> @@ -80,6 +80,21 @@ static const struct ieee80211_channel_range ieee80211_JP_channels[] = {
> IEEE80211_CHAN_RADAR),
> };
>
> +static const struct ieee80211_channel_range ieee80211_EU_channels[] = {
> + /* IEEE 802.11b/g, channels 1..13 */
> + RANGE_PWR(2412, 2472, 27, 6, 0),
This should read:
+ RANGE_PWR(2412, 2472, 20, 0, 0),
The power limit is supposed to be +20dBm in the EU, and it's EIRP so
that includes antenna gain which I've set to 0dB.
For an authoritative document you need http://www.etsi.org but their
site is down just now, so I can't find the document I want.
> + /* IEEE 802.11a, channel 36*/
> + RANGE_PWR(5180, 5180, 23, 6, 0),
> + /* IEEE 802.11a, channel 40*/
> + RANGE_PWR(5200, 5200, 23, 6, 0),
> + /* IEEE 802.11a, channel 44*/
> + RANGE_PWR(5220, 5220, 23, 6, 0),
> + /* IEEE 802.11a, channels 48..64 */
> + RANGE_PWR(5240, 5320, 23, 6, 0),
> + /* IEEE 802.11a, channels 100..140 */
> + RANGE_PWR(5500, 5700, 23, 6, 0),
> +};
> +
> #define REGDOM(_code) \
> { \
> .code = __stringify(_code), \
> @@ -90,6 +105,7 @@ static const struct ieee80211_channel_range ieee80211_JP_channels[] = {
> static const struct ieee80211_regdomain ieee80211_regdoms[] = {
> REGDOM(US),
> REGDOM(JP),
> + REGDOM(EU),
> };
>
>
--
Brian Morrison
bdm at fenrir dot org dot uk
"Arguing with an engineer is like wrestling with a pig in the mud;
after a while you realize you are muddy and the pig is enjoying it."
GnuPG key ID DE32E5C5 - http://wwwkeys.uk.pgp.net/pgpnet/wwwkeys.html
next prev parent reply other threads:[~2008-03-31 23:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 21:01 [PATCH] cfg80211: add EU regulatory domain John W. Linville
2008-03-31 22:00 ` Brian Morrison [this message]
2008-04-01 12:21 ` Johannes Berg
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=20080331230030.18da1c21@peterson.fenrir.org.uk \
--to=bdm@fenrir.org.uk \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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