From: <rmandrad@gmail.com>
To: <wens@kernel.org>
Cc: "'linux-wireless'" <linux-wireless@vger.kernel.org>,
"'wireless-regdb'" <wireless-regdb@lists.infradead.org>
Subject: RE: wireless-regdb: Allow 6ghz in the US
Date: Wed, 26 Feb 2025 09:40:47 -0000 [thread overview]
Message-ID: <001e01db8832$844ef130$8cecd390$@gmail.com> (raw)
In-Reply-To: <CAGb2v642utRqjhKth9he-jicA_E5RfYoXTPRyZaVykLNXQCXvg@mail.gmail.com>
wireless-regdb: Allow 6ghz in the US by removing NO-IR
The Federal Communications Commission on 05/26/2020 allowed for the use unlicensed use of the 6GHz band [1]. Currently the settings for US have non-IR. In order to comply with this legislation [1], the patch removes the NO-IR flag
The power limit is not increased from 12 dBm to 30 dBm to comply with the PSD requirements when using a 20 MHz channel
[1] https://www.federalregister.gov/documents/2020/05/26/2020-11236/unlicensed-use-of-the-6-ghz-band#p-66
Signed-off-by: Rudy Andram <rmandrad@gmail.com>
diff --git a/db.txt b/db.txt
index 803f1bc..ffcb0a6 100644
--- a/db.txt
+++ b/db.txt
@@ -1953,7 +1953,7 @@ country US: DFS-FCC
(5850 - 5895 @ 40), (27), NO-OUTDOOR, AUTO-BW, NO-IR
# 6g band
# https://www.federalregister.gov/documents/2020/05/26/2020-11236/unlicensed-use-of-the-6ghz-band
- (5925 - 7125 @ 320), (12), NO-OUTDOOR, NO-IR
+ (5925 - 7125 @ 320), (12), NO-OUTDOOR
# 60g band
# reference: section IV-D https://docs.fcc.gov/public/attachments/FCC-16-89A1.pdf
# channels 1-6 EIRP=40dBm(43dBm peak)
-----Original Message-----
From: Chen-Yu Tsai <wens@kernel.org>
Sent: 26 February 2025 09:16
To: rmandrad@gmail.com
Cc: linux-wireless <linux-wireless@vger.kernel.org>; wireless-regdb <wireless-regdb@lists.infradead.org>
Subject: Re: wireless-regdb: Allow 6ghz in the US
(When replying, please reply to all)
On Wed, Feb 26, 2025 at 5:05 PM <rmandrad@gmail.com> wrote:
>
> Thank you. Apologies this is the first time submitting a kernel patch.
> The original submission set NO-IR where clearly the document notes it
> is allowed as section 59 states hence the patch - with increase usage
> of 6Ghz we have now Openwrt users complaining they can't the band in
> the US due to NO-IR
>
> Shall I update the patch to only remove NO-IR and increase power to 30 dBm ?
As explained, the limit is lowered from 30 dBm to 12 dBm to comply with the PSD requirements when using a 20 MHz channel. I suspect no one would use such a narrow band, but the requirements exist and the database rule should not be written in a way that allows the user to exceed the limit, i.e. using 30 dBm on a 20 MHz channel.
So please update the patch to only remove NO-IR. You can look at previous commits to see how we put URLs in the commit message.
Thanks
ChenYu
> Thank you again
>
> -----Original Message-----
> From: Chen-Yu Tsai <wens@kernel.org>
> Sent: 26 February 2025 08:58
> To: rmandrad@gmail.com
> Cc: linux-wireless@vger.kernel.org;
> wireless-regdb@lists.infradead.org; Dennis Bland
> <dennis@dbperformance.com>; Ping-Ke Shih <pkshih@realtek.com>
> Subject: Re: wireless-regdb: Allow 6ghz in the US
>
> CC-ing Dennis, the original submitter, and also Ping-Ke, who has done a lot of 6 GHz updates, for more information.
>
> On Wed, Feb 26, 2025 at 4:03 PM <rmandrad@gmail.com> wrote:
> >
> > Allow 6ghz in the US
> >
> > https://www.federalregister.gov/documents/2020/05/26/2020-11236/unli
> > ce nsed-u se-of-the-6-ghz-band allows the use of 6ghz in the US
> > namely section
> > 59 https://www.federalregister.gov/d/2020-11236/p-66 with absolute
> > radiated power of 30 dBm for the 320 megahertz channel
>
> Please don't wrap URLs.
>
> Please see the original submission [1], which explains why the power limit is so low. Basically, neither the database nor the kernel supports specifying power spectral density limits, so we can only take the narrowest bandwidth to calculate the applicable power limit.
>
> [1]
> https://lore.kernel.org/wireless-regdb/CAPRryQp6j4UKvLZCkMAuQdaxepMBET
> QUJ1eNULJSh3ZWXC0f5Q@mail.gmail.com/
>
> > based on this remove NO-IR flag and allow 30 dBm max power
>
> The original submission mentioned NO-IR requirements, though I did not find such wording. Dennis, do you have any ideas?
>
> > Signed-off-by: Rudy Andram <rmandrad@gmail.com>
> >
> > diff --git a/db.txt b/db.txt
> > index 803f1bc..bc2b4fe 100644
> > --- a/db.txt
> > +++ b/db.txt
> > @@ -1953,7 +1953,8 @@ country US: DFS-FCC
> > (5850 - 5895 @ 40), (27), NO-OUTDOOR, AUTO-BW, NO-IR
> > # 6g band
> > #
> > https://www.federalregister.gov/documents/2020/05/26/2020-11236/unli
> > ce
> > nsed-u
> > se-of-the-6ghz-band
> > - (5925 - 7125 @ 320), (12), NO-OUTDOOR, NO-IR
> > + (5925 - 6425 @ 320), (30), NO-OUTDOOR
> > + (6525 - 6875 @ 320), (30), NO-OUTDOOR
>
> The database entry targets LPI usage instead of standard usage, which requires the presence of AFC, which is also a requirement that the database is unable to represent. And under LPI usage, the full 6GHz band (U-NII-5, 6, 7) is available.
>
>
> Thanks
> ChenYu
>
> > # 60g band
> > # reference: section IV-D
> > https://docs.fcc.gov/public/attachments/FCC-16-89A1.pdf
> > # channels 1-6 EIRP=40dBm(43dBm peak)
> >
> >
> >
>
prev parent reply other threads:[~2025-02-26 9:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 7:46 wireless-regdb: Allow 6ghz in the US rmandrad
2025-02-26 8:58 ` Chen-Yu Tsai
2025-02-26 9:09 ` Ping-Ke Shih
[not found] ` <CAPRryQobXZe5OwR=F-X0KHYyfBwUpFsi=Y5pKnENcUXTN42xAA@mail.gmail.com>
2025-03-05 8:27 ` rmandrad
[not found] ` <002d01db8da7$daf2ed50$90d8c7f0$@gmail.com>
2025-03-05 8:58 ` Chen-Yu Tsai
2025-03-05 12:18 ` Nicolas Cavallari
2025-03-05 14:36 ` rmandrad
2025-03-05 15:11 ` Chen-Yu Tsai
2025-03-05 15:27 ` rmandrad
2025-03-06 8:02 ` Johannes Berg
2025-09-09 6:12 ` Chen-Yu Tsai
2025-09-09 12:03 ` Johannes Berg
[not found] ` <000901db882d$8cb13090$a61391b0$@gmail.com>
2025-02-26 9:16 ` Chen-Yu Tsai
2025-02-26 9:40 ` rmandrad [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='001e01db8832$844ef130$8cecd390$@gmail.com' \
--to=rmandrad@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--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