From: Seth Forshee <seth.forshee@canonical.com>
To: Andrej Vlasic <andrej.vlasic0@gmail.com>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wireless-regdb: Update regulatory rules for Croatia (HR)
Date: Thu, 15 Oct 2015 13:04:08 -0500 [thread overview]
Message-ID: <20151015180408.GA31612@ubuntu-hedt> (raw)
In-Reply-To: <1444761084-4399-1-git-send-email-andrej.vlasic0@gmail.com>
On Tue, Oct 13, 2015 at 08:31:24PM +0200, Andrej Vlasic wrote:
> Update frequency allocation rules to mach data from table [1].
>
> Also increase allowed power limit for range 5150-5250 Mhz to 200mW.
>
> [1] http://tablice.hakom.hr:8280/vis?lang=en
>
> Signed-off-by: Andrej Vlasic <andrej.vlasic0@gmail.com>
> ---
> db.txt | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/db.txt b/db.txt
> index d57ea84..3b36616 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -504,11 +504,17 @@ country HN: DFS-FCC
> (5490 - 5730 @ 160), (24), DFS
> (5735 - 5835 @ 80), (30)
>
> +# Data from table of frequency allocations: http://tablice.hakom.hr:8280/vis?lang=en
> +# For 5ghz range see http://www.hakom.hr/UserDocsImages/op%C4%87e%20dozvole%20prosinac%202009.g/Opca_dozvola_85.pdf
> +# and http://www.hakom.hr/UserDocsImages/op%C4%87e%20dozvole%20prosinac%202009.g/Opca_dozvola_86.pdf
> +# and http://www.hakom.hr/UserDocsImages/op%C4%87e%20dozvole%20prosinac%202009.g/Opca_dozvola_87.pdf
> +# TPC devices on range 5250-5350 can use 200mW, and 1W on range 5470-5725.
> +
> country HR: DFS-ETSI
> - (2402 - 2482 @ 40), (20)
> - (5170 - 5250 @ 80), (20), AUTO-BW
> - (5250 - 5330 @ 80), (20), DFS, AUTO-BW
> - (5490 - 5710 @ 160), (27), DFS
> + (2400 - 2483.5 @ 40), (100 mW)
> + (5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW
> + (5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW
> + (5470 - 5725 @ 160), (500 mW), DFS
> # 60 gHz band channels 1-4, ref: Etsi En 302 567
> (57000 - 66000 @ 2160), (40)
In general the changes look okay to me and in line with the published
regulations (I couldn't read some of the documents you linked to, but
the limits do look to be in line with ERC/DEC/(01)07 and ECC/DEC/(04)08
which are referenced by the frequency allocation table).
It seems pretty arbitrary to change from dBm to mW however, especially
for those rules whose power limit isn't actually changing. I'd prefer we
leave them in dBm for consistency, in which case I think we end up with:
country HR: DFS-ETSI
(2400 - 2483.5 @ 40), (20)
(5150 - 5250 @ 80), (23), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (20), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (27), DFS
# 60 gHz band channels 1-4, ref: Etsi En 302 567
(57000 - 66000 @ 2160), (40)
If that looks fine to you then I can fix it up when I apply the patch.
Thanks,
Seth
next prev parent reply other threads:[~2015-10-15 18:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 18:31 [PATCH] wireless-regdb: Update regulatory rules for Croatia (HR) Andrej Vlasic
2015-10-15 18:04 ` Seth Forshee [this message]
2015-10-18 19:44 ` Andrej Vlašić
2015-10-22 15:00 ` Seth Forshee
-- strict thread matches above, loose matches on Subject: below --
2020-09-13 17:21 Robert Marko
2020-11-09 23:16 ` Seth Forshee
2020-11-10 10:35 ` Robert Marko
2020-11-10 14:28 ` Seth Forshee
2020-11-10 15:22 ` Robert Marko
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=20151015180408.GA31612@ubuntu-hedt \
--to=seth.forshee@canonical.com \
--cc=andrej.vlasic0@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--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