linux-wireless.vger.kernel.org archive mirror
 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 2/4] wireless-regdb: Update regulatory info for Kuwait (KW) for 2022
Date: Wed, 28 Aug 2024 16:47:04 +0800	[thread overview]
Message-ID: <20240828084706.12257-2-pkshih@gmail.com> (raw)
In-Reply-To: <20240828084706.12257-1-pkshih@gmail.com>

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

Kuwait, CITRA (Communication & Information Technology Regulatory Authority)
released Regulations for Wi-Fi service on 2022 [1] via page [2].

 * 2400 - 2483.5 MHz
   - upper limit 100 mW; 10 mW/MHz (adopt 100 mW)
 * 5150 - 5250 MHz
   - upper limit 200 mW; 10 mW/MHz (adopt 200 mW)
 * 5250 - 5350 MHz
   - upper limit 100 mW; 10 mW/MHz (adopt 100 mW)
   - DFS
 * 5470 - 5725 MHz
   - upper limit 500 mW; 50 mW/MHz (adopt 500 mW)
   - DFS
 * 5725 - 5825 MHz
   - upper limit 500 mW; 50 mW/MHz (adopt 500 mW)
   - DFS
 * 5925 - 6425 MHz
   - 200 mW
   - indoor only

[1] https://citra.gov.kw/sites/ar/Lists/CITRALaws/Attachments/14/%D8%A7%D9%84%D9%84%D8%A7%D8%A6%D8%AD%D8%A9%20%D8%A7%D9%84%D8%AA%D9%86%D8%B8%D9%8A%D9%85%D9%8A%D8%A9%20%D9%84%D8%AE%D8%AF%D9%85%D8%A9%20%D8%A7%D9%84%D9%88%D8%A7%D9%8A%20%D9%81%D8%A7%D9%8A.pdf
[2] https://citra.gov.kw/sites/ar/Pages/CITRALaws.aspx

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

diff --git a/db.txt b/db.txt
index ad8dddc9c800..50ebd50becbd 100644
--- a/db.txt
+++ b/db.txt
@@ -1050,10 +1050,14 @@ country KR: DFS-JP
 	# 60 GHz band channels 1-4
 	(57000 - 66000 @ 2160), (43)
 
+# Source:
+# https://citra.gov.kw/sites/ar/Lists/CITRALaws/Attachments/14/%D8%A7%D9%84%D9%84%D8%A7%D8%A6%D8%AD%D8%A9%20%D8%A7%D9%84%D8%AA%D9%86%D8%B8%D9%8A%D9%85%D9%8A%D8%A9%20%D9%84%D8%AE%D8%AF%D9%85%D8%A9%20%D8%A7%D9%84%D9%88%D8%A7%D9%8A%20%D9%81%D8%A7%D9%8A.pdf
 country KW: DFS-ETSI
-	(2402 - 2482 @ 40), (20)
-	(5170 - 5250 @ 80), (20), AUTO-BW
-	(5250 - 5330 @ 80), (20), DFS, AUTO-BW
+	(2400 - 2483.5 @ 40), (100 mW)
+	(5170 - 5250 @ 80), (200 mW), AUTO-BW
+	(5250 - 5350 @ 80), (100 mW), DFS, AUTO-BW
+	(5470 - 5825 @ 160), (500 mW), DFS
+	(5925 - 6425 @ 320), (200 mW), NO-OUTDOOR
 
 country KY: DFS-FCC
 	(2402 - 2482 @ 40), (20)
-- 
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 [PATCH 1/4] wireless-regdb: Update regulatory info for Serbia (SR) for 2024 Ping-Ke Shih
2024-08-28  8:47 ` Ping-Ke Shih [this message]
2024-08-30  5:11   ` [PATCH 2/4] wireless-regdb: Update regulatory info for Kuwait (KW) for 2022 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-2-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;
as well as URLs for NNTP newsgroup(s).