linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Konev <uejikov@gmail.com>
To: sforshee@kernel.org
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org
Subject: [PATCH v2] wireless-regdb: Update regulatory info for Russia (RU) on 5GHz
Date: Tue, 31 Jan 2023 19:49:09 +0700	[thread overview]
Message-ID: <CAO7DJoCeUdHzRYkXg-HXTQqYpBPijR-ZbUy_C6Lx35s-wYR-mQ@mail.gmail.com> (raw)

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..915a3b9 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), (100 mW), NO-OUTDOOR, DFS
+       (5650 - 5850 @ 160), (100 mW), NO-OUTDOOR, DFS
        # 60 GHz band channels 1-4, ref: Changes to NLA 124_Order
№129_22042015.pdf
        (57000 - 66000 @ 2160), (40), NO-OUTDOOR

-- 
2.30.2

             reply	other threads:[~2023-01-31 12:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 12:49 Eugene Konev [this message]
2023-02-13 14:48 ` [PATCH v2] wireless-regdb: Update regulatory info for Russia (RU) on 5GHz 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=CAO7DJoCeUdHzRYkXg-HXTQqYpBPijR-ZbUy_C6Lx35s-wYR-mQ@mail.gmail.com \
    --to=uejikov@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sforshee@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;
as well as URLs for NNTP newsgroup(s).