From: Seth Forshee <seth.forshee@canonical.com>
To: Dmitry Tunin <hanipouspilot@gmail.com>
Cc: wireless-regdb@lists.infradead.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] wireless-regdb: update regulatory rules for Russia (RU) on 5GHz
Date: Fri, 23 Aug 2019 14:00:19 -0500 [thread overview]
Message-ID: <20190823190019.GZ3071@ubuntu-xps13> (raw)
In-Reply-To: <1564427246-25592-1-git-send-email-hanipouspilot@gmail.com>
On Mon, Jul 29, 2019 at 10:07:26PM +0300, Dmitry Tunin wrote:
> Russian entry is incorrect. According to the last regulations document of Feb 29, 2016,
> 160 MHz channels and 802.11ad are allowed.
>
> http://rfs-rf.ru/upload/medialibrary/c1a/prilozhenie-1-k-resheniyu-gkrch-_-16_36_03.pdf
>
> Note that there was never a DFS requirement in Russia, but always was
> NO-OUTDOOR on 5GHz.
> Maximum power is 200mW that is ~23dBm on all 5GHz channels.
> Also Russia has never been regulated by ETSI.
>
> Signed-off-by: Dmitry Tunin <hanipouspilot@gmail.com>
> ---
> db.txt | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/db.txt b/db.txt
> index 37393e6..d95ed5e 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -1097,14 +1097,12 @@ country RS: DFS-ETSI
> # 60 GHz band channels 1-4, ref: Etsi En 302 567
> (57000 - 66000 @ 2160), (40)
>
> -country RU: DFS-ETSI
> +country RU:
> (2402 - 2482 @ 40), (20)
> - (5170 - 5250 @ 80), (20), AUTO-BW
> - (5250 - 5330 @ 80), (20), DFS, AUTO-BW
> - (5650 - 5730 @ 80), (30), DFS
> - (5735 - 5835 @ 80), (30)
> + (5170 - 5350 @ 160), (23), NO-OUTDOOR
> + (5650 - 5850 @ 160), (23), NO-OUTDOOR
Based on the translation I've read of the document you've linked to as
well as a couple of others, it sounds like the use of these ranges
requires TPC. Since TPC is not supported in Linux, we need to reduce the
max EIRP for these ranges to 20 dBm.
While modifying them, let's also update the 5170-5350 range to 5150-5350
to match the regulations.
Thanks,
Seth
> # 60 GHz band channels 1-4, ref: Changes to NLA 124_Order №129_22042015.pdf
> - (57000 - 66000 @ 2160), (40)
> + (57000 - 66000 @ 2160), (40), NO-OUTDOOR
>
> country RW: DFS-FCC
> (2402 - 2482 @ 40), (20)
> --
> 2.7.4
>
next prev parent reply other threads:[~2019-08-23 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 19:07 [PATCH v2] wireless-regdb: update regulatory rules for Russia (RU) on 5GHz Dmitry Tunin
2019-08-23 19:00 ` Seth Forshee [this message]
2019-08-23 19:08 ` Dmitry Tunin
2019-08-23 19:21 ` Seth Forshee
2019-08-24 5:19 ` Dmitry Tunin
-- strict thread matches above, loose matches on Subject: below --
2019-07-29 19:01 Dmitry Tunin
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=20190823190019.GZ3071@ubuntu-xps13 \
--to=seth.forshee@canonical.com \
--cc=hanipouspilot@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