From: Alexander Wilhelm <alexander.wilhelm@westermo.com>
To: linux-wireless@vger.kernel.org
Cc: wireless-regdb@lists.infradead.org
Subject: wireless-regdb: Wrong ETSI tranmit power without TPC
Date: Tue, 6 May 2025 15:13:14 +0200 [thread overview]
Message-ID: <aBoK6p1+F5ve1rC6@FUE-ALEWI-WINX> (raw)
Hello devs,
please correct me if I'm wrong. Since TPC is not used, the EU Rules dictates to
decrease the transmit power by 3 dBm on some sub-bands. For the most of the EU
countries the mW instead of dBm is used. Therefore they are halved (e.g for
Germany (DE) in commit 81d251dda3985e1088bd89f5d9f565e63ba5a30f). The problem is
that the values are then converted to dBm and rounded down and result in a wrong
supported value. Take a look at example (Germany again):
country DE: DFS-ETSI
(2400 - 2483.5 @ 40), (100 mW)
(5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
(5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW, wmmrule=ETSI
(5470 - 5725 @ 160), (500 mW), DFS, wmmrule=ETSI
# short range devices (ETSI EN 300 440-1)
(5725 - 5875 @ 80), (25 mW)
# WiFi 6E
(5945 - 6425 @ 320), (23), NO-OUTDOOR, wmmrule=ETSI
# 60 GHz band channels 1-4 (ETSI EN 302 567)
(57000 - 66000 @ 2160), (40)
For the frequencies 5250 - 5350 the power of 100 mW results it 20 dBm. Correct.
The frequencies 5470 - 5725 have a power of 500 mW. It results in 26 dBm. But I
believe 27 dBm are allowed. For the frequncies 5725 - 5875 the value of 25 mW is
also dictated. I'm not sure if I should expect 14 dBm, but I get 13 dBm.
Is there inconsistencies between dBm/mW conversions? Please give me a feedback.
Best regards
Alexander Wilhelm
next reply other threads:[~2025-05-06 13:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 13:13 Alexander Wilhelm [this message]
2025-05-16 8:15 ` wireless-regdb: Wrong ETSI tranmit power without TPC Chen-Yu Tsai
2025-05-16 8:26 ` Johannes Berg
2025-05-16 8:38 ` Johannes Berg
2025-05-16 8:39 ` Johannes Berg
2025-05-16 9:22 ` Alexander Wilhelm
2025-05-16 9:29 ` Johannes Berg
2025-05-16 9:14 ` Alexander Wilhelm
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=aBoK6p1+F5ve1rC6@FUE-ALEWI-WINX \
--to=alexander.wilhelm@westermo.com \
--cc=linux-wireless@vger.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