public inbox for wireless-regdb@lists.infradead.org
 help / color / mirror / Atom feed
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
Date: Mon, 6 Jun 2022 09:41:58 -0500	[thread overview]
Message-ID: <Yp4SNofnJOeu/tB1@ubuntu-x1> (raw)
In-Reply-To: <Yn7PFi556pM+r08j@ubuntu-x1>

On Fri, May 13, 2022 at 04:35:18PM -0500, Seth Forshee wrote:
> 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.

I've updated all rules for this range to remove AUTO-BW. I think the GB
rule is correct now.

I did a quick check of the other rules versus IR 2030, and they look
okay to me. Let me know if you see any issues I missed.

Thanks,
Seth

_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb

      reply	other threads:[~2022-06-06 14:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 19:50 [wireless-regdb] Correction of wireless-regdb for GB Ed W
2020-11-06 21:44 ` Seth Forshee
2020-11-13 18:49   ` Ed W
2020-11-20 17:54     ` Seth Forshee
2022-04-25 13:17       ` Ed W
2022-05-13 21:35         ` Seth Forshee
2022-06-06 14:41           ` Seth Forshee [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=Yp4SNofnJOeu/tB1@ubuntu-x1 \
    --to=seth@forshee.me \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lists@wildgooses.com \
    --cc=seth.forshee@canonical.com \
    --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