From: Ping-Ke Shih <pkshih@gmail.com>
To: wens@kernel.org
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org
Subject: [PATCH v3 1/3] wireless-regdb: Update regulatory info for Jordan (JO) for 2022
Date: Tue, 2 Jul 2024 14:50:58 +0800 [thread overview]
Message-ID: <20240702065100.13644-1-pkshih@gmail.com> (raw)
From: Ping-Ke Shih <pkshih@realtek.com>
The Hashemite Kingdom of Jordan, Telecommunications Regulatory Authority
issued pursuant to the provisions of Articles (12A) and (22) of the
Telecommunications Law No. 31 of 1995, as amended. [1]
The effective radiated power (EIRP) of devices used in local radio computer
networks must not exceed the following values:
- 2400-2483.5 MHz: 100 milliwatts (20 dBm)
- 5150-5350 MHz: 200 milliwatts (23 dBm), (ETSI: 5250-5350 DFS)
- 5470-5725 MHz: 1 watt (30 dBm), (ETSI: 27 dBm, indoor only, DFS)
- 5725-5875 MHz: 200 mW (23 dBm), (ETSI: indoor only)
- 5925-6425 MHz:
* 25 milliwatts (14 dBm) (for outdoor and portable devices)
* 200 milliwatts (23 dBm) (for devices operated indoors only)
- 57-71 GHz: 10 W (40 dBm)
Follow ETSI EN 301 893 [2], which specifies reduced power limit of
20 and 27 dBm for the range 5150-5350 and 5470-5725 respectively for
devices that don't implement TPC; and classifies the 5470 - 5725 MHz and
5725 - 5875 MHz ranges as indoor use only; and DFS is required for bands
5250 - 5350 Mhz and 5470 - 5725 Mhz. (Add these rules followed rules of
[1] with "ETSI:" annotation)
[1] https://trc.gov.jo/EchoBusV3.0/SystemAssets/PDF/RSMD/cb9f9a83-43a6-4e66-8432-6e02ecaf465b_RLAN%20Arabic%20%20Final%20-%20clean%20with%2057-71%20GHz.pdf
[2] https://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf
Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
---
v3:
- DFS-ETSI
- split frequency 5250 - 5350 as an individual range for DFS
v2:
- Follow ETSI EN 301 893
- add 57-71 GHz
---
db.txt | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/db.txt b/db.txt
index 61c46186919e..4d2ebe46172d 100644
--- a/db.txt
+++ b/db.txt
@@ -957,10 +957,17 @@ country JM: DFS-FCC
(5490 - 5730 @ 160), (24), DFS
(5735 - 5835 @ 80), (30)
-country JO: DFS-JP
- (2402 - 2482 @ 40), (20)
- (5170 - 5250 @ 80), (23)
- (5735 - 5835 @ 80), (23)
+# Source:
+# https://trc.gov.jo/EchoBusV3.0/SystemAssets/PDF/RSMD/cb9f9a83-43a6-4e66-8432-6e02ecaf465b_RLAN%20Arabic%20%20Final%20-%20clean%20with%2057-71%20GHz.pdf
+# ETSI EN 301 893: https://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf
+country JO: DFS-ETSI
+ (2400 - 2483.5 @ 40), (20)
+ (5150 - 5250 @ 80), (23), AUTO-BW
+ (5250 - 5350 @ 80), (23), DFS, AUTO-BW
+ (5470 - 5725 @ 80), (27), DFS, NO-OUTDOOR
+ (5725 - 5875 @ 80), (23), NO-OUTDOOR
+ (5925 - 6425 @ 320), (23), NO-OUTDOOR
+ (57000 - 71000 @ 2160), (40)
# Source:
# https://www.soumu.go.jp/main_content/000635492.pdf
--
2.25.1
next reply other threads:[~2024-07-02 6:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 6:50 Ping-Ke Shih [this message]
2024-07-02 6:50 ` [PATCH v3 2/3] wireless-regdb: Update regulatory info for Kenya (KE) for 2022 Ping-Ke Shih
2024-07-02 6:51 ` [PATCH v3 3/3] wireless-regdb: Update regulatory info for Macao (MO) for 2024 Ping-Ke Shih
2024-07-04 7:26 ` [PATCH v3 1/3] wireless-regdb: Update regulatory info for Jordan (JO) for 2022 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=20240702065100.13644-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.