From: "John W. Linville" <linville@tuxdriver.com>
To: Kurt Garloff <garloff@suse.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: Re: WLAN Regulatory Domain Germany
Date: Fri, 18 Jun 2010 14:44:32 -0400 [thread overview]
Message-ID: <20100618184431.GD6282@tuxdriver.com> (raw)
In-Reply-To: <20100525151429.GC6342@tpkurt2.garloff.de>
On Tue, May 25, 2010 at 05:14:29PM +0200, Kurt Garloff wrote:
> OK, new suggestion.
>
> 8<------------------------------------------------------------------------
>
> # Data from "Frequenznutzungsplan" (as published in April 2008), downloaded from
> # http://www.bundesnetzagentur.de/cae/servlet/contentblob/38448/publicationFile/2659/Frequenznutzungsplan2008_Id17448pdf.pdf
> # For the 5GHz range also see
> # http://www.bundesnetzagentur.de/cae/servlet/contentblob/38216/publicationFile/6579/WLAN5GHzVfg7_2010_28042010pdf.pdf
> # The values have been reduced by a factor of 2 (3db) for non TPC devices
> # (in other words: devices with TPC can use twice the tx power of this table).
> # Note that the docs do not require TPC for 5150--5250; the reduction to
> # 100mW thus is not strictly required -- however the conservative 100mW
> # limit is used here as the non-interference with radar and satellite
> # apps relies on the attenuation by the building walls only in the
> # absence of DFS; the neighbour countries have 100mW limit here as well.
>
> 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<------------------------------------------------------------------------
Is this what we want? Are you going to submit an actual patch?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-06-18 18:45 UTC|newest]
Thread overview: 19+ 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
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 [this message]
2010-11-17 21:36 ` [PATCH] wireless-regdb: update rules for DE John W. Linville
2010-11-18 18:28 ` Luis R. Rodriguez
2010-11-18 21:23 ` Michael Green
2010-11-19 2:04 ` John W. Linville
[not found] ` <20101119091450.GD12228@tpkurt2.nue.garloff.de>
2010-11-19 15:14 ` Michael Green
2010-11-19 17:12 ` Luis R. Rodriguez
2010-11-19 18:06 ` 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 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=20100618184431.GD6282@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=garloff@suse.de \
--cc=johannes@sipsolutions.net \
--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 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).