From: Ping-Ke Shih <pkshih@gmail.com>
To: wens@kernel.org
Cc: linux-wireless@vger.kernel.org,
wireless-regdb@lists.infradead.org,
avalon.vargas.centeno@est.una.ac.cr
Subject: [PATCH] wireless-regdb: Update regulatory info including bandwidth for Costa Rica (CR) for 2023
Date: Mon, 25 Aug 2025 09:47:17 +0800 [thread overview]
Message-ID: <20250825014717.6771-1-pkshih@gmail.com> (raw)
From: Ping-Ke Shih <pkshih@realtek.com>
THE PRESIDENT OF THE REPUBLIC AND THE MINISTER OF SCIENCE, INNOVATION,
TECHNOLOGY AND TELECOMMUNICATIONS released National Frequency Allocation
Plan (PNAF) No. 44010-MICITT [1], and effective date from 05/31/2023.
The table 22 shows maximum power permitted for the frequency bands:
- 2400 to 2500
36
- 5150 to 5350
30
DFS on 5250-5350
- 5470 to 5725
30
DFS on 5470-5730 (take 5MHz from next entry)
- 5725 to 5850
36
- 5850 to 5895
36
- 5895 to 5925
30
- 5925 to 7125
30, LPI, indoor only
14, VLP, indoor and outdoor
- 57,000 to 71,000
43
Avalon reported the bandwidth limitation of 20MHz causing lower throughput
than what he set country to US, and he reached PNAF about the bandwidth
limitation, resulting in no limitation currently [2].
[1] https://pgrweb.go.cr/scij/Busqueda/Normativa/Normas/nrm_texto_completo.aspx?param1=NRTC&nValor1=1&nValor2=99551&nValor3=144158&strTipM=TC
[2] https://lore.kernel.org/linux-wireless/7bfa8257d34642d7a1e35b3705720357@realtek.com/#t
Reported-by: Avalon Vargas Centeno <avalon.vargas.centeno@est.una.ac.cr>
Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
---
db.txt | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/db.txt b/db.txt
index 2a2946f8d1bb..b29e719710f4 100644
--- a/db.txt
+++ b/db.txt
@@ -476,14 +476,17 @@ country CO: DFS-FCC
# Source:
# https://storage.googleapis.com/eleoscompliance1.appspot.com/public/PNAF%20modificaci%C3%B3n%20ALCA87_30_04_2021.pdf
+# https://pgrweb.go.cr/scij/Busqueda/Normativa/Normas/nrm_texto_completo.aspx?param1=NRTC&nValor1=1&nValor2=99551&nValor3=144158&strTipM=TC
country CR: DFS-FCC
(2402 - 2482 @ 40), (36)
- (5170 - 5250 @ 20), (30)
- (5250 - 5330 @ 20), (30), DFS
- (5490 - 5730 @ 20), (30), DFS
- (5735 - 5835 @ 20), (36)
- (5875 - 5925 @ 20), (30)
+ (5150 - 5250 @ 80), (30), AUTO-BW
+ (5250 - 5350 @ 80), (30), DFS, AUTO-BW
+ (5470 - 5730 @ 160), (30), DFS
+ (5730 - 5850 @ 80), (36), AUTO-BW
+ (5850 - 5895 @ 40), (36), AUTO-BW
+ (5895 - 5925 @ 20), (30), AUTO-BW
(5925 - 7125 @ 320), (30), NO-OUTDOOR
+ (57000 - 71000 @ 2160), (43)
# Source:
# https://www.mincom.gob.cu/es/marco-legal
--
2.25.1
reply other threads:[~2025-08-25 1:48 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=20250825014717.6771-1-pkshih@gmail.com \
--to=pkshih@gmail.com \
--cc=avalon.vargas.centeno@est.una.ac.cr \
--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).