Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: <wens@kernel.org>
Cc: <linux-wireless@vger.kernel.org>, <wireless-regdb@lists.infradead.org>
Subject: [PATCH v2 3/4] wireless-regdb: Update regulatory info for Chile (CL) on 6GHz
Date: Wed, 5 Jun 2024 15:14:52 +0800	[thread overview]
Message-ID: <20240605071453.8091-3-pkshih@realtek.com> (raw)
In-Reply-To: <20240605071453.8091-1-pkshih@realtek.com>

MINISTRY OF TRANSPORT AND TELECOMMUNICATIONS; UNDERSECRETARY OF
TELECOMMUNICATIONS announced RESOLUTION 1985 EXEMPT FIXED TECHNICAL
STANDARD FOR REDUCED RANGE EQUIPMENT. Section j.1) describes access
equipment, also referred to as AP, must be for exclusive indoor use with
condition of Maximum EIRP of 30 dBm (Maximum spectral density of 5 dBm/MHz).

User terminal devices that are associated with low-power AP equipment must
operate at the following power levels of Maximum EIRP of 24 dBm
(Maximum spectral density of -1 dBm/MHz). Devices that use internal
batteries may operate outdoors, with a maximum average EIRP power of
17 dBm.

With -1 dBm/MHz for user terminal devices and smallest channel is 20 MHz,
limit 12 dBm is adopted.

[1] https://www.bcn.cl/leychile/navegar?idNorma=1109333&idParte=9841504&idVersion=&r_c=6

Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
---
v2: considering clause of -1 dBm/MHz, set limit to 12 dBm.
---
 db.txt | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/db.txt b/db.txt
index 99d3f61092b7..d3b106526252 100644
--- a/db.txt
+++ b/db.txt
@@ -395,11 +395,14 @@ country CI: DFS-FCC
 	(5490 - 5730 @ 160), (24), DFS
 	(5735 - 5835 @ 80), (30)
 
+# Source:
+# https://www.bcn.cl/leychile/navegar?idNorma=1109333&idParte=9841504&idVersion=&r_c=6
 country CL: DFS-JP
 	(2402 - 2482 @ 40), (20)
 	(5170 - 5250 @ 80), (20), AUTO-BW
 	(5250 - 5330 @ 80), (20), DFS, AUTO-BW
 	(5735 - 5835 @ 80), (20)
+	(5925 - 6425 @ 320), (12), NO-OUTDOOR
 
 # Source:
 # https://wap.miit.gov.cn/cms_files/filemanager/1226211233/attach/20219/d125301b13454551b698ff5afa49ca28.pdf
-- 
2.25.1


  parent reply	other threads:[~2024-06-05  7:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05  7:14 [PATCH v2 1/4] wireless-regdb: Update regulatory info for Malaysia (MY) for 2022 Ping-Ke Shih
2024-06-05  7:14 ` [PATCH v2 2/4] wireless-regdb: Update regulatory info for Morocco (MA) on 6GHz Ping-Ke Shih
2024-06-05  7:14 ` Ping-Ke Shih [this message]
2024-06-05  7:14 ` [PATCH v2 4/4] wireless-regdb: Update regulatory info for Mexico (MX) " Ping-Ke Shih
2024-06-05  7:44   ` Ping-Ke Shih

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=20240605071453.8091-3-pkshih@realtek.com \
    --to=pkshih@realtek.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