From: Kurt Garloff <kurt@garloff.de>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Michael Green <Michael.Green@atheros.com>,
David Quan <David.Quan@atheros.com>,
linux-wireless@vger.kernel.org
Subject: Re: WLAN Regulatory Domain Germany
Date: Thu, 20 May 2010 08:48:09 +0200 [thread overview]
Message-ID: <20100520064809.GC32757@tpkurt2.garloff.de> (raw)
In-Reply-To: <AANLkTilXo13Pn6n0n3mJONuUj50BImufADLveYAjX3YR@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2143 bytes --]
Luis,
On Wed, May 19, 2010 at 03:20:24PM -0700, Luis R. Rodriguez wrote:
> On Wed, May 19, 2010 at 10:29 AM, Kurt Garloff <kurt@garloff.de> wrote:
> > country DE:
> > # entries 279004 and 280006
> > (2400 - 2483.5 @ 40), (N/A, 100 mW)
> > # entry 303005
> > (5150 - 5250 @ 40), (N/A, 100 mW), NO-OUTDOOR
> > # entries 304002 and 305002
> > (5250 - 5350 @ 40), (N/A, 100 mW), NO-OUTDOOR, DFS
> > # entries 308002, 309001 and 310003
> > (5470 - 5725 @ 40), (N/A, 500 mW), DFS
> >
> > 8<------------------------------------------------------------------------
> >
> > (Or in db, as displayed by iw reg get)
> > country DE:
> > (2400 - 2483 @ 40), (N/A, 20)
> > (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
> > (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
> > (5470 - 5725 @ 40), (N/A, 27), DFS
> >
> > PS: I'm not subscribed, please copy responses to me.
>
> Thanks for the e-mail and your review, I've passed this to our
> regulatory gods and it is now being picked at and reviewed.
Thanks.
Two more remarks:
- Having looked at the framework how we handle this regulatory stuff
in Linux these days, it looks very reasonable to me -- good job!
- The frequencies above (from Frequenznutzungsplan = freq. util. plan)
are really the limits of the frequency ranges to be used, not channel
center freqs. So if we'd have to put possible center freqs in there
and assume 22MHz (+-11MHz) for the 2.4 GHz range, we'd need to put
2411 -- 2472.5 in the DB. Likewise, assuming 20MHz (+-10MHz for the
5GHz range, we'd specify 5160 -- 5240, 5240 -- 5340 and 5480 -- 5715),
of, for 40MHz(+-20MHz) channels, it would be 5170 -- 5230, 5230 --
5330 and 5490 -- 5705. Such values are displayed with iw reg get
for our neighbors NL, FR, ... which gave me the idea that we might
not have the real boundaries in the db, but center freqs.
That said, I'd think real boundaries make more sense, as channel
widths may evolve over time ...
Thanks,
--
Kurt Garloff, VP OPS Partner Engineering -- Novell Inc.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2010-05-20 6:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 17:29 WLAN Regulatory Domain Germany Kurt Garloff
2010-05-19 22:20 ` Luis R. Rodriguez
2010-05-20 6:48 ` Kurt Garloff [this message]
2010-05-20 7:03 ` Luis R. Rodriguez
2010-05-24 8:37 ` Johannes Berg
2010-05-25 15:14 ` Kurt Garloff
2010-05-25 15:26 ` Johannes Berg
2010-06-18 18:44 ` John W. Linville
2010-11-17 21:36 ` [PATCH] wireless-regdb: update rules for DE John W. Linville
2010-11-17 21:36 ` [wireless-regdb] " John W. Linville
2010-11-18 18:28 ` Luis R. Rodriguez
2010-11-18 18:28 ` [wireless-regdb] " Luis R. Rodriguez
2010-11-18 21:23 ` Michael Green
2010-11-18 21:23 ` [wireless-regdb] " Michael Green
2010-11-19 2:04 ` John W. Linville
2010-11-19 2:04 ` [wireless-regdb] " John W. Linville
2010-11-19 9:14 ` Kurt Garloff
2010-11-19 15:14 ` Michael Green
2010-11-19 15:14 ` [wireless-regdb] " Michael Green
2010-11-19 17:12 ` Luis R. Rodriguez
2010-11-19 17:12 ` [wireless-regdb] " Luis R. Rodriguez
2010-11-19 18:06 ` Kurt Garloff
2010-11-19 18:06 ` [wireless-regdb] " Kurt Garloff
[not found] ` <93781E992CBA7843962D8B0E7D683F3C1633484F57@SC1EXMB-MBCL.global.atheros.com>
2010-11-22 19:35 ` Luis R. Rodriguez
2010-11-22 19:36 ` Luis R. Rodriguez
2010-11-22 19:36 ` [wireless-regdb] " Luis R. Rodriguez
2010-11-22 20:22 ` Michael Green
2010-11-22 20:35 ` 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=20100520064809.GC32757@tpkurt2.garloff.de \
--to=kurt@garloff.de \
--cc=David.Quan@atheros.com \
--cc=Michael.Green@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.