From: Richard Huynh <voxlympha@gmail.com>
To: sforshee@kernel.org
Cc: wireless-regdb@lists.infradead.org,
linux-wireless@vger.kernel.org,
Richard Huynh <voxlympha@gmail.com>
Subject: [wireless-regdb] [PATCH v2] wireless-regdb: Update regulatory rules for Australia (AU)
Date: Fri, 1 Apr 2022 14:11:16 +1100 [thread overview]
Message-ID: <20220401031116.2195-1-voxlympha@gmail.com> (raw)
Changes allowing lower portion of WiFi 6E spectrum. (5925-6425)
Amendment: https://www.legislation.gov.au/Details/F2022L00249
Full text: https://www.legislation.gov.au/Details/F2022C00281
Allows for both 250mW EIRP indoors or 25mW outdoors.
However, only the former limit is defined in this commit.
Signed-off-by: Richard Huynh <voxlympha@gmail.com>
---
db.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/db.txt b/db.txt
index e887c73..a820ec8 100644
--- a/db.txt
+++ b/db.txt
@@ -121,7 +121,7 @@ country AT: DFS-ETSI
(57000 - 66000 @ 2160), (40)
# Source:
-# https://www.legislation.gov.au/Details/F2016C00432
+# https://www.legislation.gov.au/Details/F2022C00281
# Both DFS-ETSI and DFS-FCC are acceptable per AS/NZS 4268 Appendix B.
# The EIRP for DFS bands can be increased by 3dB if TPC is implemented.
# In order to allow 80MHz operation between 5650-5730MHz the upper boundary
@@ -133,6 +133,7 @@ country AU: DFS-ETSI
(5470 - 5600 @ 80), (27), DFS
(5650 - 5730 @ 80), (27), DFS
(5730 - 5850 @ 80), (36)
+ (5925 - 6425 @ 160), (24), NO-OUTDOOR
(57000 - 66000 @ 2160), (43), NO-OUTDOOR
country AW: DFS-ETSI
--
2.35.1
_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb
next reply other threads:[~2022-04-01 3:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 3:11 Richard Huynh [this message]
2022-04-02 18:57 ` [wireless-regdb] [PATCH v2] wireless-regdb: Update regulatory rules for Australia (AU) 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=20220401031116.2195-1-voxlympha@gmail.com \
--to=voxlympha@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sforshee@kernel.org \
--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