public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed W <lists@wildgooses.com>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [wireless-regdb] Correction of wireless-regdb for GB
Date: Fri, 13 Nov 2020 18:49:40 +0000	[thread overview]
Message-ID: <2a710032-f2ec-d55b-5da4-d881089fe0cd@wildgooses.com> (raw)
In-Reply-To: <20201106214446.GG6125@ubuntu-x1>

[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]

Hi Seth

Thanks for patching this. Can I also bring a later patch that I posted to your attention, the actual
patch is now out of date, but I'm posting verbatim since I think there is a 25Mhz discrepancy (?)
and also my patch is almost certainly wrong, so I'm after your guidance!! :-)

Essentially there has been a recent result of a consultation in the UK (GB) to expand wifi into 6Ghz
*AND* to NOT require DFS on high 5Ghz channels.

So in summary, the change you just made (sorry) can now be set to *NOT* need DFS in the high
channels around 5.7Ghz. More details in the links below.

In particular one of the additional frequency ranges (6Ghz) has an intended use of indoor where it
has large power outputs (and encouraged to use larger powers by request of Intel), but it is *ALSO*
allowed to be used outdoor with very low power requirements (possibly it will later fall under the
UK's allowance to use higher output power if you buy a £50 licence?). I've marked it as INDOOR-ONLY
since that seems safest - I'm unclear how to mark something for dual use?

These changes significantly expand the available 5Ghz space in the UK, so would be nice to get
upstream for general use


Notes:

https://www.ofcom.org.uk/__data/assets/pdf_file/0036/198927/6ghz-statement.pdf

https://www.ofcom.org.uk/__data/assets/pdf_file/0028/84970/ir-2030.pdf

Thanks if you might make this second change!

Ed W


On 06/11/2020 21:44, Seth Forshee wrote:
> Sorry for not responding sooner. I had started to look into this when
> you sent the message, but I had to set it aside and then forgot to pick
> it back up.


[-- Attachment #2: 0001-Update-regulatory-rules-for-UK-GB.patch --]
[-- Type: text/plain, Size: 2053 bytes --]

From ee0aad4566b206f313e92ab4ae98f786767892cd Mon Sep 17 00:00:00 2001
From: root <root@twocubed.nippynetworks.lan>
Date: Thu, 17 Sep 2020 13:31:18 +0000
Subject: [PATCH] Update regulatory rules for UK (GB)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The IR-2030 document on p47 clarifies a difference for the UK on
5725-5850Mhz from the rest of the UK. Power levels are higher and it's
possible to raise these further by purchasing a 50 GBP radio licence.

Since Jan 2020 Ofcom has solicited comments on further deregulating this
band to bring it into global alignment. DFS requirements have been
removed and a new band in the 6Ghz space has been made available with
250mW power levels (indoor, 25mW outdoor), also with no DFS requirement.

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
 	# 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
+	(5925 - 6425 @ 160), (250 mW), NO-OUTDOOR, AUTO-BW, wmmrule=ETSI
 	# 60 GHz band channels 1-6
 	(57000 - 71000 @ 2160), (40)
 
-- 
2.26.2


  reply	other threads:[~2020-11-13 18:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 19:50 Correction of wireless-regdb for GB Ed W
2020-11-06 21:44 ` [wireless-regdb] " Seth Forshee
2020-11-13 18:49   ` Ed W [this message]
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

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=2a710032-f2ec-d55b-5da4-d881089fe0cd@wildgooses.com \
    --to=lists@wildgooses.com \
    --cc=linux-wireless@vger.kernel.org \
    --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