Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <b8674e67fee2393d4c5fe9d9842028545c6adcfa.camel@sipsolutions.net>
Subject: Re: [PATCH] wireless-regdb: Update regulatory rules for Brazil (BR)
From:   Johannes Berg <johannes@sipsolutions.net>
To:     Cesar Eduardo Barros <cesarb@cesarb.eti.br>, sforshee@kernel.org
Cc:     wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Date:   Fri, 02 Sep 2022 16:53:00 +0200
In-Reply-To: <20220901232734.5488-1-cesarb@cesarb.eti.br>
References: <20220901232734.5488-1-cesarb@cesarb.eti.br>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.44.4 (3.44.4-1.fc36) 
MIME-Version: 1.0
Precedence: bulk

On Thu, 2022-09-01 at 20:27 -0300, Cesar Eduardo Barros wrote:
>=20
> +	# 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)
>=20

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.

johannes