From: Ping-Ke Shih <pkshih@realtek.com>
To: "cybersnow_2001@tutamail.com" <cybersnow_2001@tutamail.com>,
"Linux Wireless" <linux-wireless@vger.kernel.org>
Subject: RE: (RTW88, RT8812AU) TXPower enforced for regulation only and not for user preference
Date: Tue, 30 Sep 2025 00:53:50 +0000 [thread overview]
Message-ID: <5cb35a53131a4a1db0b13e429d9060a4@realtek.com> (raw)
In-Reply-To: <OaGU_Py--F-9@tutamail.com>
cybersnow_2001@tutamail.com <cybersnow_2001@tutamail.com> wrote:
> Hello,
>
> Can you look at issues regarding the WIFI TXPower being enforced by country regulation that cause problems?
> When people want to bypass 80211 regulations, we cannot do it. The original Realtek drivers permit this
> but not the included kernel RTW88 driver. I know you want your driver to be compliant to 80211 but I cannot
> set the txpower to 31.5dB on my RTL8812AU adapter. I would like that you include the max power capability
> of 3149 mdBm into the driver with a module parameter that could disable any limits. I'm forced yet to stay
> with the old driver and i'm forced to make patches to it for newer kernels... TXPower cannot be only set
> by the regulatories. It limits my hardware if i'm somewhere else. If for example I set the country HK, the
> max permitted is 36dB for 2G and 5G. But how the driver know the hardware is limited to 31.5dB?
>
As I know, driver must be not only compliant to TX power, but also band edge
and etc (need RF instrument to measure the signal). Also, larger TX power
cause lower EVM normally, so unlimitedly enlarging TX power is not a good
idea. That means if you want to lower TX power than what driver defined, it
might be fine (but still no existing interface yet). Higher TX power will be
problems of regulation and performance.
prev parent reply other threads:[~2025-09-30 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 18:03 (RTW88, RT8812AU) TXPower enforced for regulation only and not for user preference cybersnow_2001
2025-09-30 0:53 ` Ping-Ke Shih [this message]
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=5cb35a53131a4a1db0b13e429d9060a4@realtek.com \
--to=pkshih@realtek.com \
--cc=cybersnow_2001@tutamail.com \
--cc=linux-wireless@vger.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