From: Seth Forshee <sforshee@kernel.org>
To: Eugene Konev <uejikov@gmail.com>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Update regulatory info for Russia (RU) on 5GHz
Date: Mon, 30 Jan 2023 14:00:55 -0600 [thread overview]
Message-ID: <Y9gh95UAejRxQ4Oy@do-x1extreme> (raw)
In-Reply-To: <CAO7DJoAXrB8e+q2uHD6Cq6A2UV5pN0=6ieAVV+yJp0ht1bPhyg@mail.gmail.com>
On Mon, Jan 30, 2023 at 09:05:30PM +0700, Eugene Konev wrote:
> Update regulatory info for Russia on 5GHz in accordance with
> current regulatory rules.
>
> Source: https://docs.cntd.ru/document/902048009?section=text
>
> Signed-off-by: Eugene Konev <uejikov@gmail.com>
> ---
> db.txt | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/db.txt b/db.txt
> index 3f74194..9bc2c1c 100644
> --- a/db.txt
> +++ b/db.txt
> @@ -1500,10 +1500,11 @@ country RS: DFS-ETSI
> # 60 GHz band channels 1-4, ref: Etsi En 302 567
> (57000 - 66000 @ 2160), (40)
>
> -country RU:
> +# Source: https://docs.cntd.ru/document/902048009?section=text
> +country RU: DFS-ETSI
> (2400 - 2483.5 @ 40), (20)
> - (5150 - 5350 @ 160), (20), NO-OUTDOOR
> - (5650 - 5850 @ 160), (20), NO-OUTDOOR
> + (5150 - 5350 @ 160), (200 mW), NO-OUTDOOR, DFS
> + (5650 - 5850 @ 160), (200 mW), NO-OUTDOOR, DFS
Based on your earlier mail these ranges require TPC. Linux does not
support TPC, so we have to cut power limits in half in the regdb. So
these need to remain at 100 mW.
Thanks,
Seth
prev parent reply other threads:[~2023-01-30 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 14:05 [PATCH] Update regulatory info for Russia (RU) on 5GHz Eugene Konev
2023-01-30 20:00 ` Seth Forshee [this message]
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=Y9gh95UAejRxQ4Oy@do-x1extreme \
--to=sforshee@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=uejikov@gmail.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