Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Date:   Fri, 13 May 2022 16:35:18 -0500
From:   Seth Forshee <seth@forshee.me>
To:     Ed W <lists@wildgooses.com>
Cc:     Seth Forshee <seth.forshee@canonical.com>,
        wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [wireless-regdb] Correction of wireless-regdb for GB
Message-ID: <Yn7PFi556pM+r08j@ubuntu-x1>
References: <4d07581c-a3be-a3c6-bf32-7007eb45d541@wildgooses.com>
 <20201106214446.GG6125@ubuntu-x1>
 <2a710032-f2ec-d55b-5da4-d881089fe0cd@wildgooses.com>
 <20201120175444.GN5439@ubuntu-x1>
 <e7268989-03cf-ae7c-f3c6-b48fe679b790@wildgooses.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <e7268989-03cf-ae7c-f3c6-b48fe679b790@wildgooses.com>
Precedence: bulk

On Mon, Apr 25, 2022 at 02:17:57PM +0100, Ed W wrote:
> On 20/11/2020 17:54, Seth Forshee wrote:
> >> Signed-off-by: Ed Wildgoose <lists@wildgooses.com>
> >> ---
> >>  db.txt | 7 +++++--
> >>  1 file changed, 5 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/db.txt b/db.txt
> >> index ac32483..cc5ffd0 100644
> >> --- a/db.txt
> >> +++ b/db.txt
> >> @@ -588,13 +588,16 @@ country FR: DFS-ETSI
> >>  # GB: https://www.ofcom.org.uk/__data/assets/pdf_file/0019/136009/Ofcom-Information-Sheet-5-GHz-RLANs.pdf
> >>  # GB: https://www.ofcom.org.uk/__data/assets/pdf_file/0028/84970/ir-2030.pdf
> >>  # GB: https://www.ofcom.org.uk/__data/assets/pdf_file/0013/126121/Statement_Implementing-Ofcoms-decision-on-the-57-71GHz-band.pdf
> >> +# GB: https://www.ofcom.org.uk/__data/assets/pdf_file/0036/198927/6ghz-statement.pdf
> >>  country GB: DFS-ETSI
> >>  	(2400 - 2483.5 @ 40), (100 mW)
> >>  	(5150 - 5250 @ 80), (200 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
> >>  	(5250 - 5350 @ 80), (100 mW), NO-OUTDOOR, DFS, AUTO-BW, wmmrule=ETSI
> >> -	(5470 - 5725 @ 160), (500 mW), DFS, wmmrule=ETSI
> >> +	(5470 - 5730 @ 160), (500 mW), DFS, wmmrule=ETSI
> > This looks okay to me.
> >
> >>  	# short range devices (ETSI EN 300 440-1)
> >> -	(5725 - 5875 @ 80), (25 mW)
> >> +	# See UK specific notes in ir-2030.pdf, p47
> >> +	(5725 - 5850 @ 80), (200 mW), AUTO-BW, wmmrule=ETSI
> > To echo what I said above, I'm unclear whether this change is in effect
> > yet, and based what I've seen so far I think it would need to include
> > NO-OUTDOOR.
> >
> >> +	(5925 - 6425 @ 160), (250 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
> > I'm also unclear on whether this change is in effect yet.
> >
> > Thanks,
> > Seth
> >
> >>  	# 60 GHz band channels 1-6
> >>  	(57000 - 71000 @ 2160), (40)
> >>  
> >> -- 
> >> 2.26.2
> >>
> 
> Hi all, I dropped off watching this for a while....
> 
> Seems like the update to IR2030 (GB country code regulations) was re-published last year, and the
> relevant sections are in pages 32 + 34-36
> 
> My reading of this is:
> 
> - Other stuff we changed 2 years ago seems ok, caveat I'm unclear when we need to state half power
> vs using mean EIRP?

We have to use half of the maximum EIRP in cases where TPC is required
because Linux does not support TPC. This is why 5250-5350 and 5470-5730
have lower limits than what is prescribed in IR 2030.

Note that many recent rules have also included power spectral density
(PSD) limits, which can also limit the max EIRP in the database since
there's currently no support for PSD limits in Linux or wireless-regdb.
Where specified in IR 2030 they do not impose any limit beyond the max
EIRP for the minimum relevant bandwidth for our purposes (20 MHz), so
they don't end up making any difference here.

> - The 5.9-6.4Ghz range is now good for use (page 35 near the bottom), perhaps add something like:
> 
> +    (5925 - 6425 @ 160), (250 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI

This looks about right. AUTO-BW isn't necessary since there are no
adjacent rules. It looks like this was overlooked in the beginning, then
the pattern was copied.

> 
> - The 60Ghz range seems to available now, but I'm not sure what power number we should have in our
> db.txt, see page 32.
> Says "40 dBm e.i.r.p / 27 dBm maximum transmit output power"
> - There are also some geographic restrictions, not sure what we can do about those?
> 
> So something like this perhaps?:
> 
> > +	(5700 - 71000 @ 160), (40)

We have a rule for this range already that looks fine to me.

> Happy to knock this up into a patch if you can help with a little guidance (although it might be
> faster for you to just commit the 2 extra lines if you agree?)

I prefer that others write patches and I review them, since no one else
really reviews the patches and it's always harder to spot errors in your
own patches. But if you're unable to do it, I can create a patch.

I think the 5725-5850 MHz change from above can also be included too, as
long as it includes NO-OUTDOOR.

Thanks,
Seth