From: plabin@plabin.cl
To: linux-wireless@vger.kernel.org
Cc: wens@kernel.org, pkshih@realtek.com
Subject: [PATCH] wireless-regdb: Update regulatory rules for Chile (CL)
Date: Mon, 19 Oct 2026 20:13:39 -0300 [thread overview]
Message-ID: <c73bf6f8881844c599cb294398639730@purelymail.com> (raw)
Update the regulatory rules for Chile (CL) based on SUBTEL
(Undersecretary
of Telecommunications) Resolución Exenta N° 1.985 (Fija Norma Técnica de
Equipos de Alcance Reducido) and its consolidated amendments.
Source:
https://www.bcn.cl/leychile/navegar?idNorma=1109333
Key changes:
- Change DFS region from DFS-JP to DFS-FCC: SUBTEL regulations align
with ITU Region 2 / FCC standards rather than Japanese MIC rules.
- 2.4 GHz band: Align boundaries to 2400-2483.5 MHz (Article 1, j.1)
and update EIRP power limit from 20 dBm to 30 dBm (1 W).
- 5150-5250 MHz: Align lower boundary to 5150 MHz, update EIRP power
limit to 30 dBm (1 W), and add NO-OUTDOOR as Article 1, literal j
strictly restricts operation in this band to indoor enclosures.
- 5250-5350 MHz: Align upper boundary from 5330 to 5350 MHz and update
EIRP power limit to 30 dBm (1 W) with DFS (Article 1, j.1).
- 5470-5725 MHz: Add missing band authorized by Article 1, j.1 with
DFS up to 1 W EIRP. Extend upper boundary to 5730 MHz to cover
Channel 144, similar to US, TW, and CA entries.
- 5725-5850 MHz: Align boundaries from 5735-5835 to 5725-5850 MHz and
update EIRP limit to 30 dBm (1 W) (Article 1, j.1).
- 57-66 GHz band: Add 60 GHz WiGig band at 40 dBm EIRP as authorized
for short-range devices.
Signed-off-by: Patricio Labin Correa <plabin@plabin.cl>
---
Hi Chen-Yu, Ping-Ke, and linux-wireless reviewers,
This is my first time submitting a patch. I prepared this RFC to
modernize
the regulatory rules for Chile (CL), which have remained largely
untouched
since 2008.
In Chile, major ISPs (such as Movistar) deploy Wi-Fi routers
broadcasting on
Channel 100 (5500 MHz) by default. Because the 5.470-5.725 GHz band was
missing
from country CL, Linux machines cannot detect or connect to these 5 GHz
networks.
Before finalizing, I would appreciate your guidance on:
1. DFS region: I changed DFS-JP to DFS-FCC since Chile follows ITU
Region 2
and aligns with FCC standards. Does DFS-FCC look right here?
2. Power limits: SUBTEL Article 1, j.1 authorizes up to 1 W EIRP. I used
(30) dBm;
would you prefer explicit mW units (e.g. 1000 mW)?
3. Channel 144: I used (5470 - 5730 @ 160) to accommodate Channel 144,
matching
conventions in US, TW, and CA rules. Does this look good?
Thank you for your review and sorry if I'm doing something wrong.
db.txt | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/db.txt b/db.txt
index 7aff3fb..1240270 100644
--- a/db.txt
+++ b/db.txt
@@ -455,13 +455,16 @@ country CI: DFS-FCC
(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)
+# https://www.bcn.cl/leychile/navegar?idNorma=1109333
+# SUBTEL Resolución Exenta N° 1.985 (Norma Técnica de Equipos de
Alcance Reducido)
+country CL: DFS-FCC
+ (2400 - 2483.5 @ 40), (30)
+ (5150 - 5250 @ 80), (30), NO-OUTDOOR, AUTO-BW
+ (5250 - 5350 @ 80), (30), DFS, AUTO-BW
+ (5470 - 5730 @ 160), (30), DFS
+ (5725 - 5850 @ 80), (30)
(5925 - 6425 @ 320), (12), NO-OUTDOOR
+ (57000 - 66000 @ 2160), (40)
# Source:
#
https://wap.miit.gov.cn/zwgk/zcwj/wjfb/tz/art/2021/art_e4ae71252eab42928daf0ea620976e4e.html
reply other threads:[~2026-10-19 23:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c73bf6f8881844c599cb294398639730@purelymail.com \
--to=plabin@plabin.cl \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=wens@kernel.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