From: Seth Forshee <sforshee@kernel.org>
To: Cesar Eduardo Barros <cesarb@cesarb.eti.br>
Cc: Johannes Berg <johannes@sipsolutions.net>,
wireless-regdb@lists.infradead.org,
linux-wireless@vger.kernel.org
Subject: Re: [wireless-regdb] [PATCH] wireless-regdb: Update regulatory rules for Brazil (BR)
Date: Wed, 7 Sep 2022 09:52:04 -0500 [thread overview]
Message-ID: <YxiwFLWhsOtJJhrq@do-x1extreme> (raw)
In-Reply-To: <6b577581-9daf-ff11-1aaa-ff1243eb9c03@cesarb.eti.br>
On Fri, Sep 02, 2022 at 07:21:50PM -0300, Cesar Eduardo Barros wrote:
> Em 02/09/2022 11:53, Johannes Berg escreveu:
> > On Thu, 2022-09-01 at 20:27 -0300, Cesar Eduardo Barros wrote:
> > >
> > > + # This range ends at 5725 MHz, but channel 144 extends to 5730 MHz.
> > > + # Since 5725 ~ 5730 MHz belongs to the next range which has looser
> > > + # requirements, we can extend the range by 5 MHz to make the kernel
> > > + # happy and be able to use channel 144.
> > > + (5470 - 5730 @ 160), (27), DFS
> > > + (5730 - 5850 @ 80), (30)
> > >
> >
> > If you do the latter as 160 as well, and add AUTO-BW, couldn't you split
> > them at 5725 correctly? But I guess it doesn't matter anyway.
>
> This was copied from the US rules (including the four-line comment), which
> have an identical split. If AUTO-BW worked here, I'd expect the US rules to
> use it.
AUTO-BW would work, and we have countries using it for this case. Iirc
for some countries we move the split to 5730 because even though
5725-5730 is at a lower power limit the rules allow channel 144 to be
used at the power limit for 5710-5725. For the US though I think it's
just historical -- it was done that way initially, and it isn't
important enough that anyone has cared to change it.
But we do generally try to keep the rules matching the official
documents as much as possible, so for new rules we should split at 5725
and use AUTO-BW as Johannes suggested. Could you send a v2 with that
change?
Thanks,
Seth
next prev parent reply other threads:[~2022-09-07 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 23:27 [PATCH] wireless-regdb: Update regulatory rules for Brazil (BR) Cesar Eduardo Barros
2022-09-02 14:53 ` Johannes Berg
2022-09-02 22:21 ` Cesar Eduardo Barros
2022-09-07 14:52 ` Seth Forshee [this message]
2022-09-07 20:02 ` [wireless-regdb] " Cesar Eduardo Barros
2022-09-09 13:20 ` Seth Forshee
2022-09-09 22:29 ` Cesar Eduardo Barros
2022-09-10 14:33 ` Johannes Berg
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=YxiwFLWhsOtJJhrq@do-x1extreme \
--to=sforshee@kernel.org \
--cc=cesarb@cesarb.eti.br \
--cc=johannes@sipsolutions.net \
--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