Linux-mediatek Archive mirror
 help / color / mirror / Atom feed
From: Deren Wu <deren.wu@mediatek.com>
To: Chen-Yu Tsai <wens@kernel.org>
Cc: <wireless-regdb@lists.infradead.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	linux-mediatek <linux-mediatek@lists.infradead.org>,
	Deren Wu <deren.wu@mediatek.com>
Subject: [PATCH] wireless-regdb: Update regulatory rules for Taiwan (TW) on 6GHz
Date: Thu, 25 Apr 2024 17:43:13 +0800	[thread overview]
Message-ID: <8f7c6ecd8e2cd15d277435719bf993217d40f12d.1714038069.git.deren.wu@mediatek.com> (raw)

The Ministry of Transportation and Communications in Taiwan has updated
its frequency allocation rules [1], now including the 5945 ~ 6425 MHz
range for Low Power Indoor (LPI) and Very Low Power (VLP) devices. As
only one power rule can be applied to a specific frequency range, we
choose the LPI devices with a power limit of 23 dBm. There is no Dynamic
Frequency Selection (DFS) requirement.

Also update the section information for the 2.4/5/60 GHz bands
with reference [1].

[1] LP0002 Low-power Radio-frequency Devices Technical Regulations
    2024/Feb/06
    https://www.ncc.gov.tw/chinese/files/24020/538_49880_240206_3.pdf

Signed-off-by: Deren Wu <deren.wu@mediatek.com>
---
 db.txt | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/db.txt b/db.txt
index fdc2c13..6981930 100644
--- a/db.txt
+++ b/db.txt
@@ -1724,12 +1724,12 @@ country TT: DFS-FCC
 # Table of Frequency Allocations of Republic of China (Taiwan) / Feb 2017:
 #   https://www.motc.gov.tw/websitedowndoc?file=post/201702221012200.doc& \
 #	filedisplay=Table%2Bof%2Bradio%2Bfrequency%2Ballocation.doc
-# LP0002 Low-power Radio-frequency Devices Technical Regulations / 23 Aug 2016:
-#   http://www.ncc.gov.tw/english/show_file.aspx?table_name=news&file_sn=681
+# LP0002 Low-power Radio-frequency Devices Technical Regulations / 6 Feb 2024:
+#   https://www.ncc.gov.tw/chinese/files/24020/538_49880_240206_3.pdf
 country TW: DFS-FCC
-	# 2.4g band, LP0002 section 3.10.1
+	# 2.4g band, LP0002 section 4.10.1
 	(2400 - 2483.5 @ 40), (30)
-	# 5g U-NII band, LP0002 section 4.7
+	# 5g U-NII band, LP0002 section 5.7
 	# 5.15 ~ 5.25 GHz: 30 dBm for master mode, 23 dBm for clients
 	(5150 - 5250 @ 80), (23), AUTO-BW
 	(5250 - 5350 @ 80), (23), DFS, AUTO-BW
@@ -1739,7 +1739,9 @@ country TW: DFS-FCC
 	# happy and be able to use channel 144.
 	(5470 - 5730 @ 160), (23), DFS
 	(5725 - 5850 @ 80), (30)
-	# 60g band, LP0002 section 3.13.1.1 (3)(C), EIRP=40dBm(43dBm peak)
+	# 6g band, LP0002 section 5.13.1.1, EIRP=23dBm
+	(5945 - 6425 @ 320), (23), NO-OUTDOOR
+	# 60g band, LP0002 section 4.13.1.1 (1)(A), EIRP=40dBm(43dBm peak)
 	(57000 - 66000 @ 2160), (40)
  
 country TZ:
-- 
2.18.0



             reply	other threads:[~2024-04-25  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25  9:43 Deren Wu [this message]
2024-04-26  7:22 ` [PATCH] wireless-regdb: Update regulatory rules for Taiwan (TW) on 6GHz 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=8f7c6ecd8e2cd15d277435719bf993217d40f12d.1714038069.git.deren.wu@mediatek.com \
    --to=deren.wu@mediatek.com \
    --cc=linux-mediatek@lists.infradead.org \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).