From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Devin Wittmayer <lucid_duck@justthetip.ca>,
linux-wireless@vger.kernel.org
Cc: pkshih@realtek.com, johannes@sipsolutions.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH rtw-next v2 1/1] wifi: rtw89: usb: Support switching to USB 3 mode
Date: Tue, 12 May 2026 01:27:18 +0300 [thread overview]
Message-ID: <2bc415d6-f0ae-42ab-8ffa-19cfb1df5954@gmail.com> (raw)
In-Reply-To: <20260511200339.33682-1-lucid_duck@justthetip.ca>
On 11/05/2026 23:03, Devin Wittmayer wrote:
> On Mon, 2026-05-11 at 21:14 +0300, Bitterblue Smith wrote:
>> Are you quite sure you tested this?
>
> Yes. Full test matrix is in the v2 cover letter (PATCH 0/1) of
> this series:
>
Good, good. So how did you avoid the crash?
> - DWA-X1850 A1 / B1 (RTL8852AU)
> - BrosTrend AX1L / AX4L (RTL8852BU)
> - BrosTrend AX8L / EDUP AXE5400 (RTL8852CU)
>
> Six adapters, x86_64 Tiger Lake xHCI + aarch64 BCM2712 / RP1 hosts.
> 60 plug-cycles + 30+ throughput cells captured 2026-04-11 to
> 2026-05-07. USB enumeration verified at SuperSpeed (5000 Mbps) on
> every patched cell.
>
> Per-cell raw evidence for the May 2026 expanded matrix (40 iperf3
> JSON files per cell, byte-counter deltas, pre/post link state,
> pre/post USB enumeration speeds, per-iteration timestamps) at:
>
> https://github.com/Lucid-Duck/rtw89-usb3-gap/tree/main/evidence/may-2026-laptop
>
> Per-adapter summaries:
>
> https://github.com/Lucid-Duck/rtw89-usb3-gap/tree/main/adapters
>
> If the Tested-by trailer should be annotated with the specific chip
> list, I will add that when, and if, a v3 is needed.
>
> Devin
next prev parent reply other threads:[~2026-05-11 22:27 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 [this message]
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
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=2bc415d6-f0ae-42ab-8ffa-19cfb1df5954@gmail.com \
--to=rtl8821cerfe2@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lucid_duck@justthetip.ca \
--cc=pkshih@realtek.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 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.