From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Seth Forshee <seth.forshee@canonical.com>,
Anne Marcel Roorda <marcel@slowthinkers.net>
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org
Subject: Re: Update regulatory rules for NL as per ETSI EN 300 440-1
Date: Sat, 23 Apr 2016 10:30:45 +0200 [thread overview]
Message-ID: <571B32B5.1040601@broadcom.com> (raw)
In-Reply-To: <20160422135529.GA109717@ubuntu-hedt>
On 22-04-16 15:55, Seth Forshee wrote:
> On Fri, Apr 22, 2016 at 02:36:13PM +0200, Anne Marcel Roorda wrote:
>>
>> Hi,
>>
>> Below the patch to include SRD as per ETSI EN 300 440-1
>> for NL.
>>
>> Thanks,
>>
>> - marcel
>>
>> Signed-off-by: Anne Marcel Roorda <marcel@slowthinkers.net>
>>
>> diff --git a/db.txt b/db.txt
>> index e9ba21a..738e412 100644
>> --- a/db.txt
>> +++ b/db.txt
>> @@ -850,11 +850,18 @@ country NI: DFS-FCC
>> (5490 - 5730 @ 160), (24), DFS
>> (5735 - 5835 @ 80), (30)
>>
>> +# Regulation on the use of frequency space without a license and
>> +# without notification 2015
>> +#
>> +# http://wetten.overheid.nl/BWBR0036378/2015-03-05
>> +
>> country NL: DFS-ETSI
>> (2402 - 2482 @ 40), (20)
>> (5170 - 5250 @ 80), (20), NO-OUTDOOR, AUTO-BW
>> (5250 - 5330 @ 80), (20), NO-OUTDOOR, DFS, AUTO-BW
>> (5490 - 5710 @ 160), (27), DFS
>> + # short range devices (ETSI EN 300 440-1)
>> + (5725 - 5875 @ 80), (25 mW)
>> # 60 GHz band channels 1-4, ref: Etsi En 302 567
>> (57000 - 66000 @ 2160), (40)
>
> I'm looking at the document you reference as translated by Google, and
> I'm not seeing anything there to support these changes. I can't find any
> reference to ETSI 300 440-1. The section which would appear to apply
> here (article 2 paragraph o) references Annex 11 for permitted frequency
> bands, and this does not include the range that you're adding.
It does. In Annex 11, subcat 1, there is entry J that specifies the range:
J 5725 – 5875 MHz 25 mW e.i.r.p.
Regards,
Arend
> I didn't read the document in its entirety though, so I may have missed
> something. If so, could you please point me to the specific section
> which would permit operation in that range?
>
> Thanks,
> Seth
> --
> 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
>
next prev parent reply other threads:[~2016-04-23 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 12:36 Update regulatory rules for NL as per ETSI EN 300 440-1 Anne Marcel Roorda
2016-04-22 13:55 ` Seth Forshee
2016-04-22 17:12 ` Anne Marcel Roorda
2016-04-22 18:17 ` Seth Forshee
2016-04-23 8:30 ` Arend van Spriel [this message]
2016-05-02 13:43 ` Seth Forshee
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=571B32B5.1040601@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@slowthinkers.net \
--cc=seth.forshee@canonical.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).