wireless-regdb: Update regulatory rules for Czech Republic (CZ) on 5GHz

wireless-regdb: Update regulatory rules for Czech Republic (CZ) on 5GHz

[Carlos Laué]

Hello,

There seems to be outdated information in the regulatory database for C=
Z. According to the new regulatory laws, which can be found at http://w=
ww.ctu.cz/1/download/Opatreni obecne povahy/VO_R_12_08_2005_34.pdf (pag=
e 2) and http://www.ctu.cz/1/download/OOP/Rok_2007/VO_R_10_03_2007_4.pd=
f (page 3), for 5GHz the table should look like this:

5150.000 - 5250.000 ; 40.000 ; NO-OUTDOOR ; N/A ; 23.00 (200.00 mW)
5250.000 - 5350.000 ; 40.000 ; NO-OUTDOOR,DFS ; N/A ; 23.00 (200.00 mW)
5470.000 - 5725.000 ; 40.000 ; DFS ; N/A ; 30.00 (1000.00 mW)
5725.000 - 5875.000 ; 40.000 ;  ; N/A ; 14.00(25.00 mW)

if there are any difference between values in dBm and in mW, please con=
sider the value in mW as the right value.=20

* The values for 5250-5350MHz and 5470-5875MHz are valid only if the de=
vice is capable of automatic output power regulation (ie.iwconfig wlan0=
 power auto). If there isn't a way to assure this, then the maximum pow=
er output limit must be set to a value 3dB lower for ranges 5250-5350MH=
z (20dBm) and 5470-5875MHz.(27dBm).

Carlos Lau=E9
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: wireless-regdb: Update regulatory rules for Czech Republic (CZ) on 5GHz

[Johannes Berg]

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

Hi,

> There seems to be outdated information in the regulatory database for
> CZ. According to the new regulatory laws, which can be found at
> http://www.ctu.cz/1/download/Opatreni obecne
> povahy/VO_R_12_08_2005_34.pdf (page 2) and
> http://www.ctu.cz/1/download/OOP/Rok_2007/VO_R_10_03_2007_4.pdf (page
> 3), for 5GHz the table should look like this:
> 
> 5150.000 - 5250.000 ; 40.000 ; NO-OUTDOOR ; N/A ; 23.00 (200.00 mW)
> 5250.000 - 5350.000 ; 40.000 ; NO-OUTDOOR,DFS ; N/A ; 23.00 (200.00 mW)
> 5470.000 - 5725.000 ; 40.000 ; DFS ; N/A ; 30.00 (1000.00 mW)
> 5725.000 - 5875.000 ; 40.000 ;  ; N/A ; 14.00(25.00 mW)

Care to send a patch? Download
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-regdb.git;a=blob_plain;f=db.txt;hb=HEAD and edit as appropriate.

> if there are any difference between values in dBm and in mW, please
> consider the value in mW as the right value. 

As you can see in the rules for DE, you can give the values in mW too:

        (2400 - 2483.5 @ 40), (N/A, 100 mW)

I encourage you to add a comment, so that the CZ entry looks like this:

# Data from
# http://www.ctu.cz/1/download/Opatreni%20obecne%20povahy/VO_R_12_08_2005_34.pdf
# and http://www.ctu.cz/1/download/OOP/Rok_2007/VO_R_10_03_2007_4.pdf
country CZ:
	(2402 - 2482 @ 40), (N/A, 20)
...
	(5250 - 5350 @ 40), (N/A, 200 mW), NO-OUTDOOR, DFS
etc.

> * The values for 5250-5350MHz and 5470-5875MHz are valid only if the
> device is capable of automatic output power regulation (ie.iwconfig
> wlan0 power auto). If there isn't a way to assure this, then the
> maximum power output limit must be set to a value 3dB lower for ranges
> 5250-5350MHz (20dBm) and 5470-5875MHz.(27dBm).

Hmm. I don't think we have a way to capture this right now, should
probably use the lower values then.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: wireless-regdb: Update regulatory rules for Czech Republic (CZ) on 5GHz

[Johannes Berg]

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


> I encourage you to add a comment, so that the CZ entry looks like this:
> 
> # Data from
> # http://www.ctu.cz/1/download/Opatreni%20obecne%20povahy/VO_R_12_08_2005_34.pdf
> # and http://www.ctu.cz/1/download/OOP/Rok_2007/VO_R_10_03_2007_4.pdf
> country CZ:
> 	(2402 - 2482 @ 40), (N/A, 20)

that shows up on the web too, cf.
http://wireless.kernel.org/en/developers/Regulatory/Database?alpha2=DE

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[PATCH] wireless-regdb: Update regulatory rules for Czech Republic (CZ) on 5GHz

[Carlos Laué]

> Hi,
> 
> > There seems to be outdated information in the regulatory database for
> > CZ. According to the new regulatory laws, which can be found at
> > http://www.ctu.cz/1/download/Opatreni obecne
> > povahy/VO_R_12_08_2005_34.pdf (page 2) and
> > http://www.ctu.cz/1/download/OOP/Rok_2007/VO_R_10_03_2007_4.pdf (page
> > 3), for 5GHz the table should look like this:
> > 
> > 5150.000 - 5250.000 ; 40.000 ; NO-OUTDOOR ; N/A ; 23.00 (200.00 mW)
> > 5250.000 - 5350.000 ; 40.000 ; NO-OUTDOOR,DFS ; N/A ; 23.00 (200.00 mW)
> > 5470.000 - 5725.000 ; 40.000 ; DFS ; N/A ; 30.00 (1000.00 mW)
> > 5725.000 - 5875.000 ; 40.000 ;  ; N/A ; 14.00(25.00 mW)
> 
> Care to send a patch? Download
> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-regdb.git;a=blob_plain;f=db.txt;hb=HEAD
> and edit as appropriate.
> 
> > if there are any difference between values in dBm and in mW, please
> > consider the value in mW as the right value. 
> 
> As you can see in the rules for DE, you can give the values in mW too:
> 
>         (2400 - 2483.5 @ 40), (N/A, 100 mW)
> 
> I encourage you to add a comment, so that the CZ entry looks like this:
> 
> # Data from
> #
> http://www.ctu.cz/1/download/Opatreni%20obecne%20povahy/VO_R_12_08_2005_34.pdf
> # and http://www.ctu.cz/1/download/OOP/Rok_2007/VO_R_10_03_2007_4.pdf
> country CZ:
> 	(2402 - 2482 @ 40), (N/A, 20)
> ...
> 	(5250 - 5350 @ 40), (N/A, 200 mW), NO-OUTDOOR, DFS
> etc.
> 
> > * The values for 5250-5350MHz and 5470-5875MHz are valid only if the
> > device is capable of automatic output power regulation (ie.iwconfig
> > wlan0 power auto). If there isn't a way to assure this, then the
> > maximum power output limit must be set to a value 3dB lower for ranges
> > 5250-5350MHz (20dBm) and 5470-5875MHz.(27dBm).
> 
> Hmm. I don't think we have a way to capture this right now, should
> probably use the lower values then.
> 
> johannes
> 
OK, I thought we cannot guarantee the automatic power regulation, using lower values for now, it would be nice to implement the required mechanism to assure tx power regulation, but then how to define the two values? two tables, or a flag like "NO-APC -3" indicating that, without tx power regulation, there is a lower limit for tx power? 
And the patch:

 

Re: [PATCH] wireless-regdb: Update regulatory rules for Czech Republic (CZ) on 5GHz

[Johannes Berg]

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

On Fri, 2008-11-28 at 01:11 +0100, Carlos Laué wrote:

> OK, I thought we cannot guarantee the automatic power regulation,
> using lower values for now, it would be nice to implement the required
> mechanism to assure tx power regulation, but then how to define the
> two values? two tables, or a flag like "NO-APC -3" indicating that,
> without tx power regulation, there is a lower limit for tx power? 

No, it's not that trivial, needs more thought and a db change.

> And the patch:

I think you forgot something.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[PATCH] wireless-regdb: Update regulatory rules for Czech Republic (CZ) on 5GHz

[Carlos Laué]

> > OK, I thought we cannot guarantee the automatic power regulation,
> > using lower values for now, it would be nice to implement the required
> > mechanism to assure tx power regulation, but then how to define the
> > two values? two tables, or a flag like "NO-APC -3" indicating that,
> > without tx power regulation, there is a lower limit for tx power? 
> 
> No, it's not that trivial, needs more thought and a db change.

Sure, I realize that, but we should start somewhere... I think  we can discuss how to change it, change at least the db and the parser, then start making little changes all around. I'll send this idea into another e-mail to discuss about. For now, we should stay with the lower settings

> > And the patch:
> 
> I think you forgot something.
> 
> johannes

 Yes, there is definitely something missing... sorry... But I remember sending it a second time a couple of minutes later, including the patch. Perhaps something happened between Firefox and my free webmail.... restarted Firefox, let's try again.

The patch:

--- old/db.txt	2008-11-28 00:42:28.000000000 +0100
+++ new/db.txt	2008-11-28 00:48:43.000000000 +0100
@@ -141,10 +141,15 @@
 	(5250 - 5330 @ 40), (N/A, 20), DFS
 	(5490 - 5710 @ 40), (N/A, 27), DFS
 
+# Data from
+# http://www.ctu.cz/1/download/Opatreni%20obecne%20povahy/VO_R_12_08_2005_34.pdf
+# and http://www.ctu.cz/1/download/OOP/Rok_2007/VO_R_10_03_2007_4.pdf
 country CZ:
-	(2402 - 2482 @ 40), (N/A, 20)
-	(5170 - 5250 @ 40), (N/A, 20)
-	(5250 - 5330 @ 40), (N/A, 20), DFS
+	(2402 - 2482 @ 40), (N/A, 100 mW)
+	(5150 - 5250 @ 40), (N/A, 200 mW), NO-OUTDOOR
+	(5250 - 5350 @ 40), (N/A, 100 mW), NO-OUTDOOR, DFS
+	(5470 - 5725 @ 40), (N/A, 500 mW), DFS
+	(5725 - 5875 @ 40), (N/A, 25 mW)
 
 # Data from "Frequenznutzungsplan" (as published in April 2008),
 # downloaded from http://www.bundesnetzagentur.de/media/archive/13358.pdf

[PATCH v2] wireless-regdb: Update regulatory rules for Czech Republic (CZ)

[Carlos Laué]

Hi,

This is a proper git diff of the proposed changes to meet regulatory needs for Czech Republic.

- minor changes to 2.4GHz
- actual information about 5GHz 

unfortunately we shouldn't use full power on some frequencies, this is possible only if we can ensure the use of auto TX power regulation (VOR-12-08-2005-34 Article 2 g) ), staying 3dB below maximum allowed power for now (at 5250 - 5350 MHz and 5470 - 5725 MHz).

 I've found the documents (the ones in the patch) as a unofficial translation to English, hosted on the official website of the Czech Telecommunication Offiice. The informations there appears to be correct, identical to the Czech official documents. The official documents can be found at: 
http://www.ctu.eu/1/download/Opatreni%20obecne%20povahy/VO_R_12_08_2005_34.pdf
http://www.ctu.eu/1/download/OOP/Rok_2007/VO_R_12_05_2007_6.pdf
http://www.ctu.eu/1/download/OOP/Rok_2007/VO_R_10_03_2007_4.pdf


Signed-off-by: Carlos Laué <carlosl@seznam.cz>

diff --git a/db.txt b/db.txt
index 6a282b6..6cd65a2 100644
--- a/db.txt
+++ b/db.txt
@@ -141,10 +141,15 @@ country CY:
        (5250 - 5330 @ 40), (N/A, 20), DFS
        (5490 - 5710 @ 40), (N/A, 27), DFS

+# Data from http://www.ctu.eu/164/download/VOR/VOR-12-08-2005-34.pdf
+# http://www.ctu.eu/164/download/VOR/VOR-12-05-2007-6-AN.pdf
+# and http://www.ctu.eu/164/download/VOR/VOR-10-10-2008-14-AN.pdf
 country CZ:
-       (2402 - 2482 @ 40), (N/A, 20)
-       (5170 - 5250 @ 40), (N/A, 20)
-       (5250 - 5330 @ 40), (N/A, 20), DFS
+       (2400 - 2483.5 @ 40), (N/A, 100 mW)
+       (5150 - 5250 @ 40), (N/A, 200 mW), NO-OUTDOOR
+       (5250 - 5350 @ 40), (N/A, 100 mW), NO-OUTDOOR, DFS
+       (5470 - 5725 @ 40), (N/A, 500 mW), DFS
+       (5725 - 5875 @ 40), (N/A, 25 mW)

 # Data from "Frequenznutzungsplan" (as published in April 2008),
 # downloaded from http://www.bundesnetzagentur.de/media/archive/13358.pdf
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
>From linux-wireless-owner@vger.kernel.org Tue Dec  2 10:42:49 2008
Return-Path: <linux-wireless-owner@vger.kernel.org>
Received: from jmalinen.user.openhosting.com [128.177.27.249]
	by jm.kir.nu with POP3 (fetchmail-6.3.8)
	for <jm@localhost> (single-drop); Tue, 02 Dec 2008 10:42:49 +0200 (EET)
Received: from vger.kernel.org (vger.kernel.org [209.132.176.167])
	by jmalinen.user.openhosting.com (8.13.8/8.13.8) with ESMTP id mB23IHiZ005270
	for <j@w1.fi>; Mon, 1 Dec 2008 22:18:17 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752599AbYLBDSO (ORCPT <rfc822;j@w1.fi>);
	Mon, 1 Dec 2008 22:18:14 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752727AbYLBDSO
	(ORCPT <rfc822;linux-wireless-outgoing>);
	Mon, 1 Dec 2008 22:18:14 -0500
Received: from n13b.bullet.mail.mud.yahoo.com ([68.142.207.222]:29247 "HELO
	n13b.bullet.mail.mud.yahoo.com" rhost-flags-OK-OK-OK-OK)
	by vger.kernel.org with SMTP id S1753225AbYLBDSM (ORCPT
	<rfc822;linux-wireless@vger.kernel.org>);
	Mon, 1 Dec 2008 22:18:12 -0500
X-Greylist: delayed 377 seconds by postgrey-1.27 at vger.kernel.org; Mon, 01 Dec 2008 22:18:12 EST
Received: from [209.191.108.96] by n13.bullet.mail.mud.yahoo.com with NNFMP; 02 Dec 2008 03:11:55 -0000
Received: from [76.13.13.26] by t3.bullet.mud.yahoo.com with NNFMP; 02 Dec 2008 03:11:55 -0000
Received: from [76.13.10.183] by t3.bullet.mail.ac4.yahoo.com with NNFMP; 02 Dec 2008 03:11:55 -0000
Received: from [127.0.0.1] by omp124.mail.ac4.yahoo.com with NNFMP; 02 Dec 2008 03:11:55 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 198339.49210.bm@omp124.mail.ac4.yahoo.com
Received: (qmail 53228 invoked by uid 60001); 2 Dec 2008 03:11:55 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID;
  b=2ofmIXopEEozsRi2skrf5VvVtd+ZB0sUnUkspViqVDQ+7yCevnP0/UPt0NcTMKv9kHSf77E8RAr0mVbWYAWBlcTELks5oNARCBqLaEDWfKIUIX9G1uIVUZ5ISXfkGa7AUZc30JMni4zpOiOFStnbdSJJlRv294X/Lc+aGqXYFXI=;
X-YMail-OSG: REcOiyAVM1l8.8hlyhyDUX7_cwvbQSLZ4yeOwIhhx_DBEN5o6hVl2zaSyumvZNYTsUEBg3KjeZ9Gdd_YoJCbYid7N7Tq0RfTj3O4ONcYHpoiWAe05zTddW2uTYD2rxEgdCTdZKixa5u5REqoy412cljyq0kY
Received: from [125.167.124.102] by web59615.mail.ac4.yahoo.com via HTTP; Mon, 01 Dec 2008 19:11:55 PST
X-Mailer: YahooMailWebService/0.7.260.1
Date: 	Mon, 1 Dec 2008 19:11:55 -0800 (PST)
From: Irwan Siajadi <dev.bahamot@yahoo.com>
Subject: Re: ath5k: can't browse at all.
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Pavel Roskin <proski@gnu.org>,
        "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Message-ID: <63885.52788.qm@web59615.mail.ac4.yahoo.com>
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-wireless.vger.kernel.org>
X-Mailing-List: 	linux-wireless@vger.kernel.org
Status: RO
Content-Length: 3585




--- On Mon, 12/1/08, Luis R. Rodriguez <lrodriguez@atheros.com> wrote:

> From: Luis R. Rodriguez <lrodriguez@atheros.com>
> Subject: Re: ath5k: can't browse at all.
> To: "Irwan Siajadi" <dev.bahamot@yahoo.com>
> Cc: "Pavel Roskin" <proski@gnu.org>, "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
> Date: Monday, December 1, 2008, 5:11 PM
> On Sun, Nov 30, 2008 at 08:53:36AM -0800, Irwan Siajadi
> wrote:
> > --- On Tue, 11/25/08, Pavel Roskin
> <proski@gnu.org> wrote:
> > 
> > > From: Pavel Roskin <proski@gnu.org>
> > > Subject: Re: ath5k: can't browse at all.
> > > To: "Irwan Siajadi"
> <dev.bahamot@yahoo.com>
> > > Cc: linux-wireless@vger.kernel.org
> > > Date: Tuesday, November 25, 2008, 8:02 PM
> > > On Tue, 2008-11-25 at 09:24 -0800, Irwan Siajadi
> wrote:
> > >
> > > > Further testing shows that if I change from
> WPA2/AES
> > > to WPA/TIKIP, I
> > > > can finally browse. But it's still hit
> and missed,
> > > I need to reload
> > > > the pages once or twice before the pages can
> load
> > > properly.
> > >
> > > Try disabling hardware crypto in the driver:
> > >
> > > rmmod ath5k
> > > modprobe ath5k nohwcrypt=1
> > 
> > Sorry for the late reply, being busy with other
> stuffs.
> > Anyway, disabling hardware cyrpto didn't make any
> changes.
> > 
> > >
> > > In any case, check messages from wpa_supplicant. 
> Maybe
> > > it's
> > > reauthenticating very often.  If you flood ping
> the router
> > > ("ping -f"),
> > > you would probably see growing dots that
> represent lost
> > > packets.
> > 
> > Flood ping the router doesn't have any lost
> packets (although only for a
> > minute or so). And my router's log shows that the
> laptop didn't
> > re-authenticate very often.
> > 
> > I've also compiled vanilla 2.6.26 and 2.6.27 with
> ath5k (compat-wireless).
> > 
> > - 2.6.26.8 + ath5k (compat-wireless-old-2008-11-29,
> files last editted on
> > 2008-09-16):
> > -> ping shows some packets loss.
> > -> can browse any websites.
> 
> Lets focus on >= 2.6.27.
> 
> > 
> > - 2.6.27.7 + ath5k (compat-wireless-2008-11-26):
> > -> ping doesn't have any packet loss.
> > -> can't browse, browser always waiting for the
> response from the server.
> > Monitoring the traffics shows that there are tx
> packets, but there's no rx
> > packets.
> > 
> > Anything else I can try?
> 
> You say you can ping fine but... browsing doesn't
> work?? Maybe a
> firewall issue?
> 
> /etc/init.d/iptables stop
> 
> I agree with Pavel this does not seem like a driver issue.
> Do you have
> your AP configured to disable :80 TCP communication? Can
> you try a simple
> netcat server and netcat client on different ports and also
> on port 80
> just to see if its really firewall/AP configuration.


Firewall on both end (router-ap and laptop) is disabled.
I can't do netcat on the server since it's not a PC box. It's an all in 
one unit (ADSL modem+AP+router). But I did wireshark on the laptop before 
reading your email. And I can see many TCP retransmission while trying to 
browse. If you like I can attach the log and send it to you. 


As comparison, I also do wireshark while using ndiswrapper. I can find TCP 
retransmission while using ndiswrapper, but doesn't really affect browsing 
or large file transfer through SMB.


PS: If you prefer netcat, please tell me, I'll do that and send the log if 
you like.


> 
>   Luis

Irwan.



      

Different TX power settings depending on actual regdomain and auto TX power settings

[Carlos Laué]

> Od: Johannes Berg <johannes@sipsolutions.net>
> P=F8edm=ECt: Re: [PATCH] wireless-regdb: Update regulatory rules for =
Czech Republic
> (CZ) on 5GHz
> Datum: 28.11.2008 11:09:02
> On Fri, 2008-11-28 at 01:11 +0100, Carlos Lau=E9 wrote:
>=20
> > OK, I thought we cannot guarantee the automatic power regulation,
> > using lower values for now, it would be nice to implement the requi=
red
> > mechanism to assure tx power regulation, but then how to define the
> > two values? two tables, or a flag like "NO-APC -3" indicating that,
> > without tx power regulation, there is a lower limit for tx power?=20
>=20
> No, it's not that trivial, needs more thought and a db change.
>
> johannes

Yes, I'm aware of it.=20

To make things clear and simple, I'll resume why we need such a feature=
:
In Czech Republic, and maybe on other countries, one can transmit twice=
 more eirp on 5GHz (on some frequencies) with automatic TX power manage=
ment enabled than without such feature. For the Czech Republic,the limi=
t is 3dB lower for devices without such feature(ie. half the output pow=
er). So it would be nice if users could use all available TX power, wit=
hout breaking the law, and without having to bother.
I'm using APC for automatic TX power management (as if one sets "iwconf=
ig wlan0 txpower auto") on the text below.

Perhaps the first thing we have to do is to change a little the DB and =
the parser. Adding a entry telling that, for the desired frequency, the=
re can be "n" dB more TX power with APC enabled than without APC, or to=
 define a second limit.
=20
The right thing to do would be to start at lower TX power settings, aft=
erwards CRDA would check if the driver is capable of APC, and if it is,=
 and it is enabled, than it could rise the TX power settings. That woul=
d assure that a driver unaware of APC "feature-enabled-feedback" won't =
 get the higher tx power settings than is legal to use.

Problems could arise when userspace tools i.e. iwconfig are used to dis=
able APC, then the card should start transmitting with less power. We c=
ould just warn users about that, but to make things automatic would be =
nice. Maybe even the drivers will need a little touch to have them gene=
rating a udev event when APC settings changes, and then let CRDA make t=
he right choice of max TX power setting.

It seems that iwtxpower setting are now handled by mac80211. It would b=
e nice to see this feature when it gets to cfg80211....=20

I'm downloading the wireless-testing git tree right now, but it will ta=
ke a while at 18KB/s...

Carlos Lau=E9
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: wireless-regdb: Update regulatory rules for Czech Republic (CZ) on 5GHz

[Carlos Laué]

Hello,

Sorry for my late reply.

On the Czech regulatory's website, they have a page deliberately speaki=
ng about usage of 5.725-5.850GHz frequencies.=20
 "V oblasti 5 GHz je mo=C5=BEn=C3=BD provoz podle VO-R/12/08.2005-34 a =
VO-R/10/03.2007-4 v p=C3=A1smu 5,15=E2=80=935,35 GHz (pouze uvnit=C5=99=
 budov), v p=C3=A1smu 5,470=E2=80=935,725 GHz (standard IEEE 802.11a) a=
 s mal=C3=BDm v=C3=BDkonem (25 mW e.i.r.p.) t=C3=A9=C5=BE v p=C3=A1smu =
5,725=E2=80=935,875 GHz.".=20
The last part means "with small output power (25mW e.i.r.p.) also in th=
e 5,725=E2=80=935,875 GHz frequency range."
 On the VO-R/10/03.2007-4 they also state that those frequencies are IS=
M, but maximum allowed e.i.r.p. is 25mW.=20

I don't know if tthis is compliant with EN301 893 or other EU laws.

So for now we should let those dubious frequencies off the table.
Also, let's do not penalize ourselves by 3dB, I've noted that, for othe=
r EU countries, the power limit is the highest allowed (Thanks Luis for=
 explaining what  "TPC compliant" means).=20

I'm sending the patch in the next e-mail.

Carlos

> ------------ P=C5=AFvodn=C3=AD zpr=C3=A1va ------------
> Od: Michael Green <Michael.Green@Atheros.com>
> P=C5=99edm=C4=9Bt: RE: wireless-regdb: Update regulatory rules for Cz=
ech Republic (CZ) on
> 5GHz
> Datum: 04.12.2008 22:27:26
> ----------------------------------------
> Thanks Luis,
>=20
> The VO_R_10_03_2007_4.pdf shows 5.725-5.850 (and also 2.4-2.483) unde=
r SRD rules
> (Short range device) like for wireless microphones, radio control toy=
s and
> similar. That's why the tx limit is 25mW EIRP.  You will see similar =
in many
> other European and global frequency tables.   This is not used for WL=
AN
> operation.  Some non-European countries do have ISM band (5.725-5.850=
) included
> in their frequency table. Although not specifically for WLAN use, we =
do in those
> cases enable this upper band for possible use by APs, since the power=
 limits are
> usually 1W or more.  But trust me, for Europe in this band, we should=
 not enable
> this band for any 802.11 product type. This is already reflected in t=
he CRDA
> tables for all the countries. So nothing new here.
>=20
>=20
> The VO_R_12_08_2005_34.pdf doc clearly shows the WLAN rules in the ta=
ble that
> you referred.  These match up to the usual rules frequency table publ=
ished by
> other EU countries and the limits follow the EN301 893 spec.  It's al=
l good.=20
> The channel settings for this country should be same as used for all =
the other
> European countries (i.e. 5.15-5.35 & 5.47-5.725 with DFS/TPC).
>=20
> The tx power levels are worth discussing more.  Even though the Europ=
ean
> countries are harmonized on EN301 893 which enforces 200mW EIRP in 5.=
15-5.35 and
> 1W EIRP in 5.470-5.725, vendors must not blindly set new hardware to =
transmit at
> these upper limits.
>=20
> Each board design must undergo conformance testing to the applicable =
RF
> conformance spec (in this case 301 893) at which time the vendor will=
 discover
> that various other tests in the conformance spec will limit the achie=
vable
> compliant tx power for that design and it's associated antennas (i.e.=
 power
> spectral density, spurious emissions, etc.  So using 200mW and 1W EIR=
P in code
> may be fine as an upper limit, fail safe, users of the code / hardwar=
e
> developers must be educated to ensure awareness that there is no univ=
ersal
> "compliant tx power" that you can assign for a country that applies t=
o all the
> different hardware out there.
>=20
> Michael Green
> Atheros Communications, Inc.
> mgreen@atheros.com
> Desk:   +1-781-400-1491
> Mobile: +1-508-380-4921
>=20
> -----Original Message-----
> From: Luis R. Rodriguez [mailto:mcgrof@gmail.com]
> Sent: Thursday, December 04, 2008 3:52 PM
> To: Michael Green
> Cc: Johannes Berg; John W. Linville; Carlos Lau=C3=A9
> Subject: Re: wireless-regdb: Update regulatory rules for Czech Republ=
ic (CZ) on
> 5GHz
>=20
> On Thu, Dec 4, 2008 at 12:42 PM, Michael Green <Michael.Green@atheros=
=2Ecom>
> wrote:
> >
> > Thanks,
> >
> > a) Can someone pls email me the pdf's. I had no success trying to r=
etrieve
> from the regulator's site.
> >
> > b) I am glad to give opinion once I read the original docs.  But fo=
r now, some
> initial thoughts...
> >
> > By "automatic output power regulation" I believe you refer to what =
the
> standards call TPC (transmit power control).  For European and most o=
ther
> regions that include TPC in their rules, it is now basically a  hand =
waving at
> enforcing a true TPC feature. For Europe compliance any vendor who sh=
ows in the
> lab that the client device is capable of being set to lower tx levels=
 (even
> manually be end user), then device is considered compliant, even thou=
gh, the
> shipping product may never actually be set as such by end user.  So i=
n effect,
> no one really penalizes themselves the 3dB when testing against the t=
x power
> limit in the European specs.
> >
> > And use of 5.725-5.850 by 802.11 devices for Czech Rep. sounds dubi=
ous to me.=20
> So I look forward to seeing the docs.
> >
> > So please let me read the Czech spec you mention and I can compare =
against the
> EN301 893 which is the true pan-European conformance spec which is ge=
nerally the
> target we use for compliance in 5GHz.   Thanks for your patience.
>=20
> Michael, I've downloaded and attached them to this e-mail. They are i=
n CZ though
> so they are all jiberish to me. I'm also CC'ing the person who sent t=
he patch,
> as this conversation would probably be more productive with him invol=
ved.
>=20
>   Luis
>=20
>=20
>=20
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html