From: Seth Forshee <seth.forshee@canonical.com>
To: Ed W <lists@wildgooses.com>
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] Correction of wireless-regdb for GB
Date: Fri, 6 Nov 2020 15:44:46 -0600 [thread overview]
Message-ID: <20201106214446.GG6125@ubuntu-x1> (raw)
In-Reply-To: <4d07581c-a3be-a3c6-bf32-7007eb45d541@wildgooses.com>
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.
On Thu, Jul 02, 2020 at 08:50:41PM +0100, Ed W wrote:
> Hi, I think that the wireless regdb for GB domain can be corrected:
>
> According to Ofcom, in 2017 the rules were updated for the 5725-5850Ghz
> range to allow a power output of 200mW (the max power output is much higher
> still for fixed wireless where a £50 licence is purchased)
>
> Reference to the latest Ofcom document is here (IR-2030):
>
> https://www.ofcom.org.uk/__data/assets/pdf_file/0028/84970/ir-2030.pdf
>
>
> My reading of this is that DFS is currently required and I *assume* also the
> wmm would be the same as the rest of the range. I'm not sure if this rule
> needs an AUTO-BW?
AUTO-BW doesn't make sense here, however it does look like the 5470 -
5725 rule could be expanded to 5730 to allow channel 144 to be used.
I agree that it looks like DFS is required, and also TPC which will
require us to use 100 mW as the max EIRP. Afaik the wmmrule doesn't
apply to the 5.8 GHz band, so I think that isn't required.
I'll send out a patch soon with these updates.
Thanks,
Seth
> (Note also that Ofcom opened a proposal to remove the DFS requirement on
> this frequency band (and to add new 5Ghz bands). Results of this are due
> later in 2020.)
>
>
> Therefore I think that the db.txt should say:
>
>
> |
>
> country GB: DFS-ETSI
> ...
>
> # Reference (IR-2030)
> (5725 - 5875 @ 80), (200 mW), DFS, AUTO-BW, wmmrule=ETSI
>
> |
>
> |Could someone appropriate please check this and update upstream.|
>
> |
> |
>
> |Thanks|
>
> |Ed W
> |
>
> ||
>
>
> _______________________________________________
> wireless-regdb mailing list
> wireless-regdb@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/wireless-regdb
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next prev parent reply other threads:[~2020-11-06 21:44 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 [this message]
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
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=20201106214446.GG6125@ubuntu-x1 \
--to=seth.forshee@canonical.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lists@wildgooses.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