From: "sforshee@kernel.org" <sforshee@kernel.org>
To: Eric Sellman <GAK_ACTION@live.com>
Cc: "wireless-regdb@lists.infradead.org"
<wireless-regdb@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [wireless-regdb] wireless-regdb: Update regulatory rules for USA on 5GHz
Date: Fri, 31 Mar 2023 16:36:10 -0500 [thread overview]
Message-ID: <ZCdSShqbJQ43gZZR@do-x1extreme> (raw)
In-Reply-To: <SJ0PR22MB249552E61991E3B2FAC911978F8F9@SJ0PR22MB2495.namprd22.prod.outlook.com>
On Fri, Mar 31, 2023 at 08:30:09PM +0000, Eric Sellman wrote:
> First, I would like to state that I live in the USA And that this is my first time submitting a correction to the wireless-regdb.
>
> According to this list here >> https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/tree/db.txt#n1727
>
> I only see VHT160 allowed to be utilized for 5500mhz to 5640mhz but there is no mention of VH160 being allowed for use with 5180 to 5320mhz.
>
> And according to this presentation here > https://transition.fcc.gov/oet/ea/presentations/files/may17/31-Part-15-Panel-UNII-UpdatesDT.pdf
>
> And this paragraph from this FCC document here > https://www.federalregister.gov/d/2014-09279/p-65
>
> "Band Straddling" is allowed with U-NII-1 and U-NII-2A. 5150mhz to 5330mhz
>
> Therefore, I would like you to add to the db that 5180 to 5320 can be used with vht160.
You are correct, however the kernel rejects the database if the max
bandwidth for a range exceeds the size of the range for a given rule. So
unfortunately we can't set the max bandwidth to 160 MHz.
Thanks,
Seth
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next prev parent reply other threads:[~2023-03-31 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 20:30 [wireless-regdb] wireless-regdb: Update regulatory rules for USA on 5GHz Eric Sellman
2023-03-31 21:36 ` sforshee [this message]
[not found] ` <SJ0PR22MB24959C931D27BDB56488B1DF8F8F9@SJ0PR22MB2495.namprd22.prod.outlook.com>
2023-04-03 16:19 ` sforshee
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=ZCdSShqbJQ43gZZR@do-x1extreme \
--to=sforshee@kernel.org \
--cc=GAK_ACTION@live.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