From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH rtw-next v2 00/11] wifi: rtw89: Add support for RTL8922AU
Date: Tue, 21 Apr 2026 01:18:21 +0000 [thread overview]
Message-ID: <07888d2c1f9c41258627bdf6aede14d2@realtek.com> (raw)
In-Reply-To: <7c97c857607f41df912558194103d34c@realtek.com>
Ping-Ke Shih <pkshih@realtek.com> wrote:
>
> Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> > On 20/04/2026 11:20, Ping-Ke Shih wrote:
> > >
> > > Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> > >> Two people have tested MLO since v1. It doesn't explode, so I dropped
> > >> the patch to disable MLO. (It doesn't work very well with MLO, but
> > >> ¯\_(ツ)_/¯)
> > >
> > > Could you share the link they did? We can check them internally.
> > >
> > > Ping-Ke
> > >
> > >
> > >
> >
> > One reports that it works fine:
> >
> > https://github.com/morrownr/USB-WiFi/issues/494#issuecomment-4276727919
> >
> > One reports constant disconnections and strange errors like
> > "sec cam entry is empty":
>
> I think this is because TX packet with a security key, but it was deleted
> because of "(Reason: 2=PREV_AUTH_NOT_VALID)".
We are addressing a MLO problem related to power save. Please try to disable
power save to see if any improve.
>
> >
> > https://github.com/morrownr/rtw89/issues/23#issuecomment-4226769914
>
> I will try if we have an Asus BT8 (org firmware).
>
> Ping-Ke
prev parent reply other threads:[~2026-04-21 1:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-19 13:39 [PATCH rtw-next v2 00/11] wifi: rtw89: Add support for RTL8922AU Bitterblue Smith
2026-04-19 13:40 ` [PATCH rtw-next v2 01/11] wifi: rtw89: usb: Support 2 bulk in endpoints Bitterblue Smith
2026-04-19 13:40 ` [PATCH rtw-next v2 02/11] wifi: rtw89: Fix rtw89_usb_ops_mac_lv1_rcvy() for RTL8922AU Bitterblue Smith
2026-04-19 13:42 ` [PATCH rtw-next v2 03/11] wifi: rtw89: Fix rtw89_usb_ops_mac_pre_init() " Bitterblue Smith
2026-04-19 13:43 ` [PATCH rtw-next v2 04/11] wifi: rtw89: Fix rtw89_usb_ops_mac_post_init() " Bitterblue Smith
2026-04-19 13:43 ` [PATCH rtw-next v2 05/11] wifi: rtw89: usb: Enable RX aggregation " Bitterblue Smith
2026-04-20 8:38 ` Ping-Ke Shih
2026-04-19 13:44 ` [PATCH rtw-next v2 06/11] wifi: rtw89: Fix rtw8922a_pwr_{on,off}_func() for USB Bitterblue Smith
2026-04-19 13:45 ` [PATCH rtw-next v2 07/11] wifi: rtw89: Let hfc_param_ini have separate settings for USB 2/3 Bitterblue Smith
2026-04-20 8:40 ` Ping-Ke Shih
2026-04-19 13:45 ` [PATCH rtw-next v2 08/11] wifi: rtw89: Add rtw8922a_hfc_param_ini_usb{2,3} Bitterblue Smith
2026-04-19 13:46 ` [PATCH rtw-next v2 09/11] wifi: rtw89: Add rtw8922a_dle_mem_usb{2,3} Bitterblue Smith
2026-04-19 13:47 ` [PATCH rtw-next v2 10/11] wifi: rtw89: Add rtw8922au.c Bitterblue Smith
2026-04-20 8:41 ` Ping-Ke Shih
2026-04-19 13:49 ` [PATCH rtw-next v2 11/11] wifi: rtw89: Enable the new rtw89_8922au module Bitterblue Smith
2026-04-20 8:20 ` [PATCH rtw-next v2 00/11] wifi: rtw89: Add support for RTL8922AU Ping-Ke Shih
2026-04-20 18:22 ` Bitterblue Smith
2026-04-21 1:09 ` Ping-Ke Shih
2026-04-21 1:18 ` Ping-Ke Shih [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=07888d2c1f9c41258627bdf6aede14d2@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--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