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] wifi: rtw89: hw_scan: Don't let the operating channel be last
Date: Thu, 20 Nov 2025 03:17:05 +0000 [thread overview]
Message-ID: <a4fa21a5b7494a439075690d7ae2b99b@realtek.com> (raw)
In-Reply-To: <9e053524-3ab0-4d8f-9c08-1a2d0caa1892@gmail.com>
Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> On 18/11/2025 04:17, Ping-Ke Shih wrote:
> > Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> >> Scanning can be offloaded to the firmware. To that end, the driver
> >> prepares a list of channels to scan, including periodic visits back to
> >> the operating channel, and sends the list to the firmware.
> >>
> >> When the channel list is too long to fit in a single H2C message, the
> >> driver splits the list, sends the first part, and tells the firmware to
> >> scan. When the scan is complete, the driver sends the next part of the
> >> list and tells the firmware to scan.
> >>
> >> When the last channel that fit in the H2C message is the operating
> >> channel something seems to go wrong in the firmware. It will
> >> acknowledge receiving the list of channels but apparently it will not
> >> do anything more. The AP can't be pinged anymore. The driver still
> >> receives beacons, though.
> >>
> >> One way to avoid this is to split the list of channels before the
> >> operating channel.
> >>
> >> Affected devices:
> >>
> >> * RTL8851BU with firmware 0.29.41.3
> >> * RTL8832BU with firmware 0.29.29.8
> >> * RTL8852BU with firmware 0.29.29.8
>
> I made a mistake here. It should be:
>
> RTL8851BU
> RTL8832BU
> RTL8852BE
I'll re-spin commit message with this information.
>
> The report about the RTL8852BE came from a user who doesn't have the
> card anymore, unfortunately.
>
> Actually, since I wrote that commit message I acquired RTL8851BE and
> I can reproduce the problem with that.
>
I don't know why our site can't reproduce this issue. Since this patch
can help your and no obvious increasing scan time, I will take this
patch and send pull-request to 6.18-rc6.
next prev parent reply other threads:[~2025-11-20 3:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 22:54 [PATCH rtw] wifi: rtw89: hw_scan: Don't let the operating channel be last Bitterblue Smith
2025-11-18 2:17 ` Ping-Ke Shih
2025-11-18 22:21 ` Bitterblue Smith
2025-11-20 3:17 ` Ping-Ke Shih [this message]
2025-11-20 3:49 ` Ping-Ke Shih
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=a4fa21a5b7494a439075690d7ae2b99b@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