From: Eric Sellman <gak_action@live.com>
To: "sforshee@kernel.org" <sforshee@kernel.org>
Cc: "wireless-regdb@lists.infradead.org"
<wireless-regdb@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: wireless-regdb: Update regulatory rules for canada on 5GHz
Date: Sat, 1 Apr 2023 05:33:25 +0000 [thread overview]
Message-ID: <SJ0PR22MB24952C980D15D984F0CEB61E8F8C9@SJ0PR22MB2495.namprd22.prod.outlook.com> (raw)
In-Reply-To: <SJ0PR22MB2495707E5FC7EF2334A699BC8F8C9@SJ0PR22MB2495.namprd22.prod.outlook.com>
My apologies but I have made a mistake.
My previous submission about Canada is invalid. The weather frequency range has already been avoided.
Here is the correct information I meant to share with you.
https://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf10971.html#s6
"Devices with occupied bandwidths which overlap different bands shall comply with all operational requirements for each band."
https://semfionetworks.com/blog/5ghz-regulations-in-canada-2018-update/
Canada still permits the lower 5ghz frequencies to be used for VHT 160. But it's missing according to the information for the Canadian profile in line 326
https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/tree/db.txt#n326.
And I wanted to mention that for 5150 - 5250 on line 328, the transmit power has been increased to 1 watt or "30 dBm" according to this document here.
https://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf11294.html
next prev parent reply other threads:[~2023-04-01 5:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 2:11 wireless-regdb: Update regulatory rules for canada on 5GHz Eric Sellman
2023-04-01 5:33 ` Eric Sellman [this message]
2023-04-01 8:26 wireless-regdb: Update regulatory rules for Canada " Eric Sellman
2023-04-16 13:13 ` sforshee
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=SJ0PR22MB24952C980D15D984F0CEB61E8F8C9@SJ0PR22MB2495.namprd22.prod.outlook.com \
--to=gak_action@live.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;
as well as URLs for NNTP newsgroup(s).