All of lore.kernel.org
 help / color / mirror / Atom feed
From: Louis Kotze <loukot@gmail.com>
To: wireless-regdb@lists.infradead.org
Cc: wens@kernel.org, Louis Kotze <loukot@gmail.com>
Subject: [PATCH] wireless-regdb: Remove DFS flag from 60 GHz band for Togo (TG)
Date: Mon, 27 Jul 2026 10:59:53 +0200	[thread overview]
Message-ID: <20260727085953.356259-1-loukot@gmail.com> (raw)

Commit aad0c26 ("wireless-regdb: Update regulatory info for Togo (TG)
for 2022") added a DFS flag to every band in the Togo entry, including
the 57-66 GHz band.

The source regulation, ARCEP Decision N° 226/ARCEP/DG/22 of 30 December
2022, Annexe 2 section 9 ("Dispositifs de transmission de données à
large bande"), states for the 57-66 GHz row:

  57 - 66 GHz | PIRE de 40 dBm et densité de 13 dBm/MHz | Des
  techniques d'accès au spectre et d'atténuation des interférences
  doivent être utilisées. | Les installations extérieures fixes sont
  exclues.

Unlike the 5150-5350 MHz and 5470-5850 MHz rows, which explicitly
require "des techniques de sélection automatique de fréquences (DFS)",
the 57-66 GHz row requires only generic spectrum access and
interference mitigation techniques. DFS is not mentioned. There is no
radar service to protect in this band, and ETSI EN 302 567 does not
specify DFS for it.

The same commit also set DFS on the 2400-2483.5 MHz and 5925-6425 MHz
rows. Those are left as they are: the decision does print "(DFS)" in
both, so dropping the flag there would go further than the source
allows, even though DFS is a 5 GHz radar-avoidance mechanism and reads
oddly in those bands. The 60 GHz row is the only one with no basis in
the text.

Drop the DFS flag accordingly, and normalise the missing space in the
bandwidth field on the same line.

Reference:
  https://arcep.tg/wp-content/uploads/2022/12/Decision-226-22-Determinant-les-categories-et-conditions-techniques-dexploitation-des-appareils-de-faible-puissance-et-de-faible-portee.pdf
  (Annexe 2, section 9, page 21)

Signed-off-by: Louis Kotze <loukot@gmail.com>
---
 db.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/db.txt b/db.txt
index 72f7900..c6217fa 100644
--- a/db.txt
+++ b/db.txt
@@ -1962,7 +1962,7 @@ country TG: DFS-ETSI
 	(5150 - 5350 @ 80), (20), DFS
 	(5470 - 5850 @ 160), (27), DFS
 	(5925 - 6425 @ 320), (23), DFS, NO-OUTDOOR
-	(57000 - 66000 @2160), (40), DFS
+	(57000 - 66000 @ 2160), (40)
 
 # Source:
 # https://ratchakitcha.soc.go.th/documents/140D100S0000000004000.pdf
-- 
2.55.0



             reply	other threads:[~2026-07-27  9:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27  8:59 Louis Kotze [this message]
2026-07-27  9:02 ` [PATCH] wireless-regdb: Remove DFS flag from 60 GHz band for Togo (TG) 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=20260727085953.356259-1-loukot@gmail.com \
    --to=loukot@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.