All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Garloff <garloff@suse.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, "Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: Re: WLAN Regulatory Domain Germany
Date: Tue, 25 May 2010 17:14:29 +0200	[thread overview]
Message-ID: <20100525151429.GC6342@tpkurt2.garloff.de> (raw)
In-Reply-To: <1274690246.3743.20.camel@jlt3.sipsolutions.net>

[-- Attachment #1: Type: text/plain, Size: 3761 bytes --]

Johannes,

On Mon, May 24, 2010 at 10:37:26AM +0200, Johannes Berg wrote:
> > 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 devcies
> > # (in other words: devices with TPC can use twice the tx power of this table).
> > 
> > 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
> 
> I haven't verified the entries in the Frequenznutzungsplan itself, but
> according to the second document this seems fine. I think there ought to
> be a comment in the db.txt file indicating the rationale for using 100mW
> rather than 200mW.
                                                                                              
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<------------------------------------------------------------------------

Can we actually put several entries covering the same frequency range?
Then we could put 200mW for DFS and 100mW for non-DFS.
This would also address the next issue you raise ...

> Also note that there are different requirements depending on the channel
> bandwidth, which will eventually come up in Linux too. But I think for
> that we need the new database format for that ... yet another thing to
> do before we can support 5/10 MHz channels.

Indeed. For 5150 -- 5350, the spectral power density may not exceed
10mW/MHz (and overall emitted power in the range per device not 200mW);
this gives a limit of 200mW for 20MHz channels or 100mW if no TPC is 
used for 5250 -- 5350. (For 5470--5725 use 5x those values.)
I'm not aware of WLAN devices with narrower channels yet, but if they 
come into existence, we'd have to reflect it somehow ...

Best,
-- 
Kurt Garloff, VP OPS Partner Engineering -- Novell Inc.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2010-05-25 15:19 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
2010-05-20  7:03     ` Luis R. Rodriguez
2010-05-24  8:37 ` Johannes Berg
2010-05-25 15:14   ` Kurt Garloff [this message]
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=20100525151429.GC6342@tpkurt2.garloff.de \
    --to=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 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.