From: Ping-Ke Shih <pkshih@gmail.com>
To: wens@kernel.org
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org
Subject: [PATCH 1/5] wireless-regdb: Update regulatory info for New Zealand (NZ) for 2022
Date: Fri, 5 Jul 2024 14:06:09 +0800 [thread overview]
Message-ID: <20240705060613.28909-1-pkshih@gmail.com> (raw)
From: Ping-Ke Shih <pkshih@realtek.com>
Radiocommunications Regulations (General User Radio Licence for Short Range
Devices) Notice 2022 listed spectrum:
2400.0000 - 2483.5000
* e.i.r.p. 0 dBW (1 W)
5150.0000 - 5350.0000
* the maximum power is 0 dBW (1 W) e.i.r.p. and
the maximum permitted power spectral density is -13 dBW/MHz
(17 dBm/Hz, 50 mW/MHz) e.i.r.p.
* 5250 - 5350 MHz, If Transmitter Power Control is not used, then the
maximum power (e.i.r.p.) value shall be reduced by 3 dB.
5470.0000 - 5725.0000
* 5470 - 5725 MHz, transmitter peak power must not exceed -6 dBW (250 mW)
If Transmitter Power Control is not used, then the maximum power
(e.i.r.p.) value must be reduced by 3 dB.
5725.0000 - 5850.0000
* 5725 - 5850 MHz, the transmitter peak power must not exceed 0 dBW (1 W)
and the power spectral density must not exceed 17 dBm/MHz.
5925.0000 - 6425.0000
* the maximum power is -6 dBW (24 dBm, 250 mW ) e.i.r.p. and
the maximum permitted power spectral density is -19 dBW/MHz
(11 dBm/MHz, 12.6 mW/MHz) e.i.r.p. for low power devices.
Only be used indoors.
* the maximum power is -16 dBW (14 dBm, 25 mW ) e.i.r.p. and
the maximum permitted power spectral density is -29 dBW/MHz
(1 dBm/MHz, 1.26 mW/MHz) e.i.r.p. for very low power devices.
Very Low Power applications.
57000.0000 - 71000.0000
* for devices transmitting at 10 dBW e.i.r.p or less,
the power spectral density must not exceed -7 dBW/MHz e.i.r.p. and
the maximum transmit power must not exceed -3 dBW at the antenna port
or ports.
* for devices transmitting greater than 10 dBW e.i.r.p., the power
spectral density shall not exceed 8 dBW/MHz e.i.r.p and antennas with
a gain greater than 30 dBi shall be used.
[1] https://gazette.govt.nz/notice/id/2022-go3100
Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
---
db.txt | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/db.txt b/db.txt
index d7592c299c62..266ba2d48731 100644
--- a/db.txt
+++ b/db.txt
@@ -1416,12 +1416,16 @@ country NP: DFS-JP
(5250 - 5330 @ 80), (20), DFS, AUTO-BW
(5735 - 5835 @ 80), (20)
+# Source:
+# https://gazette.govt.nz/notice/id/2022-go3100
country NZ: DFS-ETSI
- (2402 - 2482 @ 40), (30)
- (5170 - 5250 @ 80), (17), AUTO-BW
- (5250 - 5330 @ 80), (24), DFS, AUTO-BW
- (5490 - 5730 @ 160), (24), DFS
- (5735 - 5835 @ 80), (30)
+ (2400 - 2483.5 @ 40), (30)
+ (5150 - 5250 @ 80), (30), AUTO-BW
+ (5250 - 5350 @ 80), (27), DFS, AUTO-BW
+ (5470 - 5730 @ 160), (21), DFS
+ (5725 - 5850 @ 80), (30)
+ (5925 - 6425 @ 320), (24), NO-OUTDOOR
+ (57000 - 71000 @ 2160), (40)
country OM: DFS-ETSI
(2402 - 2482 @ 40), (20)
--
2.25.1
next reply other threads:[~2024-07-05 6:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 6:06 Ping-Ke Shih [this message]
2024-07-05 6:06 ` [PATCH 2/5] wireless-regdb: Update regulatory info for Peru (PE) on 6GHz Ping-Ke Shih
2024-07-18 4:41 ` Chen-Yu Tsai
2024-07-05 6:06 ` [PATCH 3/5] wireless-regdb: Update regulatory info for Qatar (QA) " Ping-Ke Shih
2024-07-18 5:04 ` Chen-Yu Tsai
2024-07-05 6:06 ` [PATCH 4/5] wireless-regdb: Update regulatory info for El Salvador (SV) " Ping-Ke Shih
2024-07-18 4:43 ` Chen-Yu Tsai
2024-07-05 6:06 ` [PATCH 5/5] wireless-regdb: Update regulatory info for Togo (TG) for 2022 Ping-Ke Shih
2024-07-18 5:02 ` Chen-Yu Tsai
2024-07-19 3:07 ` Ping-Ke Shih
2024-07-18 4:37 ` [PATCH 1/5] wireless-regdb: Update regulatory info for New Zealand (NZ) " Chen-Yu Tsai
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=20240705060613.28909-1-pkshih@gmail.com \
--to=pkshih@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wens@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;
as well as URLs for NNTP newsgroup(s).