linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@gmail.com>
To: wens@kernel.org
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org
Subject: [PATCH v2 4/4] wireless-regdb: Update regulatory info for Honduras (HN) for 2023
Date: Mon,  2 Sep 2024 16:23:04 +0800	[thread overview]
Message-ID: <20240902082304.52326-4-pkshih@gmail.com> (raw)
In-Reply-To: <20240902082304.52326-1-pkshih@gmail.com>

From: Ping-Ke Shih <pkshih@realtek.com>

Honduras, Telecommunication Commission (CONATEL) modified national note
HND40A on 2023 [1], which Wireless Access System/Radio Local Area Network
(WAS/RLAN) have a general license to operate in frequency ranges:

 * 902 - 928 MHz
 * 2400 - 2483.5 MHz
 * 5150 - 5250 MHz
 * 5250 - 5350 MHz
 * 5470 - 5725 MHz
 * 5725 - 5850 MHz
 * 5925 - 6425 MHz (*)
   - By [3] clause 65, "maximum power spectral density for low power indoor
     client devices in this band is 6 dB below the limit for access
     points (or -1 dBm/MHz based on the adopted PSD limit)."
     Then, 12 dBm is adopted.
   - By [3] section 15.407 General technical requirements, (d) Operational
     restrictions for 6 GHz U-NII devices, (5), "an exception exists for
     transmitting brief messages to an access point when attempting to
     join its network after detecting a signal that confirms that
     an access point is operating on a particular channel."
     Then, NO-IR flag is set.
 * 24.05 - 24.25 GHz
 * 57 - 71 GHz (*)
   - By [4] footer 952, "limits the average EIRP of 60 GHz transmitters to
     40 dBm and the peak EIRP to 43 dBm."
     Then, 40 dBm is adopted.

Article 5 of resolution NR006/23 [2] mentioned Recognition of Standards and
International Standards including FCC, which limits and ranges of FCC are
used due to lack of limits [1], but only newly add freqnecy ranges marked
by asterisk (*).

[1] https://www.conatel.gob.hn/doc/Regulacion/resoluciones/2023/NR05-23.pdf
[2] https://www.conatel.gob.hn/doc/Regulacion/resoluciones/2023/NR006-23.pdf
[3] https://www.federalregister.gov/documents/2020/05/26/2020-11236/unlicensed-use-of-the-6ghz-band
[4] https://docs.fcc.gov/public/attachments/FCC-16-89A1.pdf

Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
---
v2:
  - add FCC source references for 5925 - 6425 MHz and 57 - 71 GHz, and
    update commit messages accordingly.
---
 db.txt | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/db.txt b/db.txt
index 0be933c86c8a..c7341b5596dc 100644
--- a/db.txt
+++ b/db.txt
@@ -819,12 +819,16 @@ country HK: DFS-ETSI
 	(5730 - 5850 @ 80), (36)
 	(5925 - 6425 @ 160), (14)
 
+# Source:
+# https://www.conatel.gob.hn/doc/Regulacion/resoluciones/2023/NR05-23.pdf
 country HN: DFS-FCC
 	(2402 - 2482 @ 40), (20)
 	(5170 - 5250 @ 80), (17), AUTO-BW
 	(5250 - 5330 @ 80), (24), DFS, AUTO-BW
 	(5490 - 5730 @ 160), (24), DFS
 	(5735 - 5835 @ 80), (30)
+	(5925 - 6425 @ 320), (12), NO-OUTDOOR, NO-IR
+	(57240 - 71000 @ 2160), (40)
 
 country HR: DFS-ETSI
 # HR as part of EU/CEPT accepted decisions 2005/513/EC (5GHz RLAN, EN 301 893)
-- 
2.25.1


  parent reply	other threads:[~2024-09-02  8:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02  8:23 [PATCH v2 1/4] wireless-regdb: Update regulatory info for Serbia (SR) for 2024 Ping-Ke Shih
2024-09-02  8:23 ` [PATCH v2 2/4] wireless-regdb: Update regulatory info for Kuwait (KW) for 2022 Ping-Ke Shih
2024-09-02  8:23 ` [PATCH v2 3/4] wireless-regdb: Update regulatory info for Israel (IL) for 2021 Ping-Ke Shih
2024-09-02  8:23 ` Ping-Ke Shih [this message]
2024-09-30  7:27 ` [PATCH v2 1/4] wireless-regdb: Update regulatory info for Serbia (SR) for 2024 Chen-Yu Tsai
2024-09-30  7:44 ` 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=20240902082304.52326-4-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).