From: Mohamed Aashif <maashif011@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: wireless-regdb@lists.infradead.org, pkshih@gmail.com,
Mohamed Aashif <maashif011@gmail.com>
Subject: [PATCH v3] wireless-regdb: Update regulatory rules for Sri Lanka (LK)
Date: Mon, 18 May 2026 13:17:43 +0530 [thread overview]
Message-ID: <20260518074743.179402-1-maashif011@gmail.com> (raw)
In-Reply-To: <CAHrRpu=-ngPpe2MsmWz0gQq1VVxbr9L0+jUos3o62wPUY-wXqQ@mail.gmail.com>
Update Sri Lanka regulatory domain based on the RTTE Type Approval
Rules 2020 from the Telecommunications Regulatory Commission of
Sri Lanka (TRC).
Source: https://www.trc.gov.lk/content/files/licensing/RTTE_GAZETTE-English.pdf
Key changes:
- Change DFS region from FCC to ETSI (document references ETSI
standards EN 300 328 and EN 301 893 as the applicable radio
interface standards)
- 2.4 GHz: expand to 2400-2483.5 MHz at 23 dBm
- 5150-5250 MHz: 23 dBm
- 5250-5350 MHz: 20 dBm with DFS (no TPC, 3 dB reduction per EN 301 893)
- 5470-5725 MHz: 27 dBm with DFS (no TPC, per EN 301 893)
- 5725-5875 MHz: 24 dBm with DFS (per ETSI EN 302 502)
Note: The TRC gazette conflicts internally by allowing 30 dBm for
5725-5875 MHz while citing EN 301 893 (which doesn't cover this band).
Lacking TRC clarification, we conservatively default to the ETSI
EN 302 502 limits (24 dBm).
Signed-off-by: Mohamed Aashif <maashif011@gmail.com>
---
Great, thanks. Removed DFS from 5150-5250 MHz.
Changes in v3:
- Corrected the table caption in the source comment to "Table 2 - Applicable Standards- Wireless"
- Removed DFS flag from 5150-5250 MHz
Changes in v2:
- Split 5150-5350 MHz into 5150-5250 MHz (23 dBm) and 5250-5350 MHz
(20 dBm), adding AUTO-BW to both.
- Applied a 3 dB reduction to 5250-5350 MHz and 5470-5725 MHz (now
27 dBm) to comply with ETSI limits since TPC is unsupported.
- Capped 5725-5875 MHz at 24 dBm per ETSI EN 302 502.
db.txt | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/db.txt b/db.txt
index fdc2c13..8038f5a 100644
--- a/db.txt
+++ b/db.txt
@@ -1058,12 +1058,15 @@ country LI: DFS-ETSI
# 60 GHz band channels 1-4 (ETSI EN 302 567)
(57000 - 66000 @ 2160), (40)
-country LK: DFS-FCC
- (2402 - 2482 @ 40), (20)
- (5170 - 5250 @ 20), (17)
- (5250 - 5330 @ 20), (24), DFS
- (5490 - 5730 @ 20), (24), DFS
- (5735 - 5835 @ 20), (30)
+# Source:
+# https://www.trc.gov.lk/content/files/licensing/RTTE_GAZETTE-English.pdf
+# Sri Lanka RTTE Type Approval Rules 2020, Table 2 - Applicable Standards- Wireless
+country LK: DFS-ETSI
+ (2400 - 2483.5 @ 40), (23)
+ (5150 - 5250 @ 80), (23), AUTO-BW
+ (5250 - 5350 @ 80), (20), DFS, AUTO-BW
+ (5470 - 5725 @ 160), (27), DFS
+ (5725 - 5875 @ 80), (24), DFS
# Source:
# http://lca.org.ls/images/documents/lesotho_national_frequency_allocation_plan.pdf
--
2.54.0
next prev parent reply other threads:[~2026-05-18 7:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 15:41 [PATCH] wireless-regdb: Update regulatory rules for Sri Lanka (LK) Mohamed Aashif
2026-05-13 5:58 ` Ping-Ke Shih
2026-05-16 10:00 ` [PATCH v2] " Mohamed Aashif
2026-05-18 7:22 ` Ping-Ke Shih
2026-05-18 7:47 ` Mohamed Aashif [this message]
2026-05-18 9:00 ` [PATCH v3] " Ping-Ke Shih
2026-05-19 6:51 ` Chen-Yu Tsai
2026-05-19 7:18 ` 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=20260518074743.179402-1-maashif011@gmail.com \
--to=maashif011@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@gmail.com \
--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