From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: wireless-regdb@lists.infradead.org
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 5/7] wireless-regdb: optimize two of ES's rules
Date: Thu, 31 Oct 2013 16:07:39 +0100 [thread overview]
Message-ID: <5272723B.4090006@gmail.com> (raw)
hi Luis,
This patch is incompatible with my ("pending")patch:
http://lists.infradead.org/pipermail/wireless-regdb/2013-February/000136.html
thanks,
---cortamorena---
Subject: [PATCH] wireless-regdb: change Max_EIRP in 5150-5250 for ES (Spain)
I did cut&paste from DE rules, but DE lowers the limit
in 5150-5250 to 100mW for "neighborhood reasons" [1].
Even when 200mW is completely legal in DE.
put 200mW, as Spanish law says:
Banda 5150 – 5350 MHz: En esta banda el uso por el servicio móvil en sistemas de
acceso inalámbrico incluyendo comunicaciones electrónicas y redes de área local, se
restringe para su utilización únicamente en el interior de recintos. La potencia isotrópica
radiada equivalente máxima será de 200 mW (p.i.r.e.), siendo la densidad máxima de
p.i.r.e. media de 10 mW/MHz en cualquier banda de 1 MHz. Este valor se refiere a la
potencia promediada sobre una ráfaga de transmisión ajustada a la máxima potencia
Orden ITC/332/2010, de 12 de febrero, por la que se aprueba el cuadro
nacional de atribución de frecuencias (CNAF):
https://www.boe.es/diario_boe/txt.php?id=BOE-A-2010-2719
https://www.boe.es/boe/dias/2010/02/19/pdfs/BOE-A-2010-2719.pdf
search for:
UN - 85 RLANs y datos en 2400 a 2483,5 MHz (pag. 213)
UN - 128 RLANs en 5 GHz (pag. 232)
more info at "Cuadro nacional de atribución de frecuencias (CNAF)":
http://www.minetur.gob.es/telecomunicaciones/espectro/paginas/cnaf.aspx
[1] http://marc.info/?l=linux-wireless&m=127429049514439
Cc: John W. Linville <linville@tuxdriver.com>
Cc: Luis R. Rodriguez <mcgrof@frijolero.org>
Cc: wireless-regdb@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
---
db.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/db.txt b/db.txt
index c5861b8..6f618c0 100644
--- a/db.txt
+++ b/db.txt
@@ -269,7 +269,7 @@ country EG:
country ES: DFS-ETSI
(2400 - 2483.5 @ 40), (N/A, 100 mW)
- (5150 - 5250 @ 40), (N/A, 100 mW), NO-OUTDOOR
+ (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
# 60 gHz band channels 1-4, ref: Etsi En 302 567
--
1.7.11.7
---end---
next reply other threads:[~2013-10-31 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 15:07 Xose Vazquez Perez [this message]
2013-10-31 20:00 ` [PATCH 5/7] wireless-regdb: optimize two of ES's rules Luis R. Rodriguez
2013-10-31 20:21 ` Xose Vazquez Perez
-- strict thread matches above, loose matches on Subject: below --
2013-10-30 21:45 [PATCH 0/7] wireless-regdb: DFS regions and optimizations Luis R. Rodriguez
2013-10-30 21:45 ` [PATCH 5/7] wireless-regdb: optimize two of ES's rules Luis R. Rodriguez
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=5272723B.4090006@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@do-not-panic.com \
--cc=wireless-regdb@lists.infradead.org \
/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).