From: Devin Wittmayer <lucid_duck@justthetip.ca>
To: pkshih@realtek.com, linux-wireless@vger.kernel.org
Cc: rtl8821cerfe2@gmail.com, johannes@sipsolutions.net,
linux-kernel@vger.kernel.org,
Devin Wittmayer <lucid_duck@justthetip.ca>
Subject: Re: [PATCH rtw-next v2 1/1] wifi: rtw89: usb: Support switching to USB 3 mode
Date: Mon, 11 May 2026 19:54:44 -0700 [thread overview]
Message-ID: <20260512025444.49247-1-lucid_duck@justthetip.ca> (raw)
In-Reply-To: <e3ae58133549411e9eeb88c7c6ffbfaa@realtek.com>
On Tue, 2026-05-12 at 01:35 +0000, Ping-Ke Shih wrote:
> As commit message, only RTL8832BU and RTL8832CU were tested, and WiFi 7
> was not neither. I'd give positive list instead.
Agreed. Tested chip set for this patch:
Bitterblue's bench (per the commit body):
RTL8852B: RTL8832BU
RTL8852C: RTL8832CU
My side (per the v2 cover letter matrix):
RTL8852A: D-Link DWA-X1850 A1 (8852AU)
RTL8852A: D-Link DWA-X1850 B1 (8852AU)
RTL8852B: BrosTrend AX1L (8832BU)
RTL8852B: BrosTrend AX4L (8832BU)
RTL8852C: BrosTrend AX8L (8832CU)
RTL8852C: EDUP AXE5400 (8832CU)
v3 will gate on RTL8852A / RTL8852B / RTL8852C. RTL8851B stays out
because no RTL8851B variant has USB 3 hardware (per the in-patch
comment), so there is nothing to switch to.
WiFi 7 in rtw89 appears to be exclusively BE-generation as far as
I am aware (RTL8922A, RTL8922D). v2's AX-gen code (R_AX_PAD_CTRL2
writes) would not execute for BE-gen chips, so no WiFi 7 chip
appears testable for this patch by construction.
Devin
prev parent reply other threads:[~2026-05-12 2:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 5:44 [PATCH 0/1] wifi: rtw89: usb: Support switching to USB 3 mode Lucid Duck
2026-05-08 5:44 ` [PATCH 1/1] " Lucid Duck
2026-05-08 6:59 ` Zenm Chen
2026-05-11 10:55 ` [PATCH 0/1] " Bitterblue Smith
2026-05-11 16:08 ` [PATCH rtw-next v2 " Devin Wittmayer
2026-05-11 16:08 ` [PATCH rtw-next v2 1/1] " Devin Wittmayer
2026-05-11 17:26 ` Johannes Berg
2026-05-11 18:03 ` Devin Wittmayer
2026-05-12 1:25 ` Ping-Ke Shih
2026-05-11 18:14 ` Bitterblue Smith
2026-05-11 20:03 ` Devin Wittmayer
2026-05-11 22:27 ` Bitterblue Smith
2026-05-12 0:35 ` Devin Wittmayer
2026-05-12 8:48 ` Bitterblue Smith
2026-05-12 1:35 ` Ping-Ke Shih
2026-05-12 2:54 ` Devin Wittmayer [this message]
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=20260512025444.49247-1-lucid_duck@justthetip.ca \
--to=lucid_duck@justthetip.ca \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=rtl8821cerfe2@gmail.com \
/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