public inbox for wireless-regdb@lists.infradead.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@gmail.com>
To: wens@kernel.org
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org
Subject: [PATCH 1/4] wireless-regdb: Update regulatory info for Serbia (SR) for 2024
Date: Wed, 28 Aug 2024 16:47:03 +0800	[thread overview]
Message-ID: <20240828084706.12257-1-pkshih@gmail.com> (raw)

From: Ping-Ke Shih <pkshih@realtek.com>

Serbia government released radio frequency range on February 5, 2024 [1].
Based on Article 100, paragraph 5 of the Law on Electronic Communications
and Article 17, paragraph 1 and Article 42, paragraph 1 of the Law on
Government.

 * 2400 - 2483.5 MHz
   - 20 dBm
   - EN 302 328
 * 5150 - 5350 MHz
   - 23 dBM (Without TPC)
   - 5250 - 5350 MHz, DFS
   - EN 301 893
 * 5470 - 5725 MHz
   - 27 dBm (Without TPC)
   - 5470 - 5725 MHz, DFS
   - EN 301 893
 * 5925 - 6425 MHz
   - 23 dBm, LPI
   - EN 303 687

[1] https://www.ratel.rs/uploads/documents/empire_plugin/Uredba%20o%20utvrdjivanju%20Plana%20namene%20radiofrekvencijskih%20opsega.pdf
[2] EN 302 328 https://www.etsi.org/deliver/etsi_en/300300_300399/300328/02.02.02_60/en_300328v020202p.pdf
[3] EN 302 066 https://www.etsi.org/deliver/etsi_en/302000_302099/302066/02.02.00_20/en_302066v020200a.pdf
[4] EN 301 893 https://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf
[5] EN 303 687 https://www.etsi.org/deliver/etsi_en/303600_303699/303687/01.01.01_60/en_303687v010101p.pdf

Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
---
 db.txt | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/db.txt b/db.txt
index 9a55f6b8cc98..ad8dddc9c800 100644
--- a/db.txt
+++ b/db.txt
@@ -1758,11 +1758,14 @@ country SN: DFS-FCC
 	(5490 - 5730 @ 160), (24), DFS
 	(5735 - 5835 @ 80), (30)
 
+# Source:
+# https://www.ratel.rs/uploads/documents/empire_plugin/Uredba%20o%20utvrdjivanju%20Plana%20namene%20radiofrekvencijskih%20opsega.pdf
 country SR: 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), (20)
+	(5150 - 5250 @ 80), (23), AUTO-BW
+	(5250 - 5350 @ 80), (23), DFS, AUTO-BW
+	(5470 - 5725 @ 160), (27), DFS
+	(5925 - 6425 @ 320), (23), NO-OUTDOOR
 
 # Source:
 # https://www.siget.gob.sv/actualizacion-de-cuadro-nacional-de-atribucion-de-frecuencias-t-0408-2023/
-- 
2.25.1



             reply	other threads:[~2024-08-28  8:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-28  8:47 Ping-Ke Shih [this message]
2024-08-28  8:47 ` [PATCH 2/4] wireless-regdb: Update regulatory info for Kuwait (KW) for 2022 Ping-Ke Shih
2024-08-30  5:11   ` Chen-Yu Tsai
2024-08-28  8:47 ` [PATCH 3/4] wireless-regdb: Update regulatory info for Israel (IL) for 2021 Ping-Ke Shih
2024-08-30  1:07   ` Chen-Yu Tsai
2024-08-28  8:47 ` [PATCH 4/4] wireless-regdb: Update regulatory info for Honduras (HN) for 2023 Ping-Ke Shih
2024-08-30  5:15   ` Chen-Yu Tsai
2024-08-29 23:23 ` [PATCH 1/4] wireless-regdb: Update regulatory info for Serbia (SR) for 2024 Chen-Yu Tsai

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=20240828084706.12257-1-pkshih@gmail.com \
    --to=pkshih@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wens@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