From: Louis Kotze <loukot@gmail.com>
To: K900 <me@0upti.me>
Cc: Chen-Yu Tsai <wens@kernel.org>,
Valeriy Kosikhin <vkosikhin@gmail.com>,
wireless-regdb@lists.infradead.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wireless-regdb: allow 320MHz channel width for Russia
Date: Tue, 28 Apr 2026 09:44:47 +0200 [thread overview]
Message-ID: <20260428074500.ru-320-review-resend@gmail.com> (raw)
In-Reply-To: <20250708-russia-320-v1-1-53641e8dd417@0upti.me>
ChenYu, thanks for the ping on this one.
Cross-checked against SCRF 22-65-05 (which added 5925-6425 MHz to the
2007 spectrum allocation, Appendix 2):
Section 2 ("Devices with direct sequence spread spectrum and other
modulation types") for 5925-6425 MHz specifies:
LPI: max EIRP 200 mW, max PSD 10 mW/MHz, indoor only,
with automatic power control
VLP: max EIRP 25 mW, max PSD 1.3 mW/MHz, indoor only
No channel-width restriction is specified for this category. The
only width cap (less than 20 MHz) applies to the FHSS subsection,
not to DSSS / 802.11-style modulation.
SCRF 23-68-03 §3.1 later replaced "automatic power control" with
"LBT mode" globally in that appendix, which the 802.11 CCA mechanism
satisfies.
320 MHz operation at the 200 mW LPI cap gives 0.625 mW/MHz, well under
the 10 mW/MHz PSD ceiling, so the wider channel stays compliant on
both EIRP and PSD limits. Per regdb convention of encoding the
spectrum allocation ceiling and leaving per-standard equipment
certification to drivers, the bandwidth widening is sound.
Reviewed-by: Louis Kotze <loukot@gmail.com>
Note that the patch base predates the recent RU power update (commit
6873bfe in wens/wireless-regdb), which changed 5925-6425 from 100 mW
to 200 mW, so this needs a rebase on current HEAD before it can be
applied.
Regards,
Louis
next prev parent reply other threads:[~2026-04-28 7:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 11:00 [PATCH] wireless-regdb: allow 320MHz channel width for Russia K900
2026-04-28 7:44 ` Louis Kotze [this message]
2026-04-28 8:16 ` Ilya K
2026-04-28 9:23 ` 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=20260428074500.ru-320-review-resend@gmail.com \
--to=loukot@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=me@0upti.me \
--cc=vkosikhin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox