From: Ping-Ke Shih <pkshih@realtek.com>
To: "wens@kernel.org" <wens@kernel.org>,
"rmandrad@gmail.com" <rmandrad@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"wireless-regdb@lists.infradead.org"
<wireless-regdb@lists.infradead.org>,
Dennis Bland <dennis@dbperformance.com>
Subject: RE: wireless-regdb: Allow 6ghz in the US
Date: Wed, 26 Feb 2025 09:09:10 +0000 [thread overview]
Message-ID: <ff6ad414457e4b1cb68e834978a553c3@realtek.com> (raw)
In-Reply-To: <CAGb2v65490c1m3W_1RkxJ-E7Q=3V_K8xqS2jmd6awcOdzWHXzQ@mail.gmail.com>
Chen-Yu Tsai <wens@kernel.org> wrote:
>
> > based on this remove NO-IR flag and allow 30 dBm max power
>
> The original submission mentioned NO-IR requirements, though I did not
> find such wording. Dennis, do you have any ideas?
>
FYI. The description below in [1]
In all cases, 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.
[1] https://www.federalregister.gov/documents/2020/05/26/2020-11236/unlicensed-use-of-the-6-ghz-band
next prev parent reply other threads:[~2025-02-26 9:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 7:46 wireless-regdb: Allow 6ghz in the US rmandrad
2025-02-26 8:58 ` Chen-Yu Tsai
2025-02-26 9:09 ` Ping-Ke Shih [this message]
[not found] ` <CAPRryQobXZe5OwR=F-X0KHYyfBwUpFsi=Y5pKnENcUXTN42xAA@mail.gmail.com>
2025-03-05 8:27 ` rmandrad
[not found] ` <002d01db8da7$daf2ed50$90d8c7f0$@gmail.com>
2025-03-05 8:58 ` Chen-Yu Tsai
2025-03-05 12:18 ` Nicolas Cavallari
2025-03-05 14:36 ` rmandrad
2025-03-05 15:11 ` Chen-Yu Tsai
2025-03-05 15:27 ` rmandrad
2025-03-06 8:02 ` Johannes Berg
2025-09-09 6:12 ` Chen-Yu Tsai
2025-09-09 12:03 ` Johannes Berg
[not found] ` <000901db882d$8cb13090$a61391b0$@gmail.com>
2025-02-26 9:16 ` Chen-Yu Tsai
2025-02-26 9:40 ` rmandrad
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=ff6ad414457e4b1cb68e834978a553c3@realtek.com \
--to=pkshih@realtek.com \
--cc=dennis@dbperformance.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rmandrad@gmail.com \
--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