From: Carl Quist <equalizerjr@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: [PATCH rtw-next] wifi: rtw88: 8723d: add iface combination
Date: Fri, 23 Oct 2026 20:17:24 +0000 [thread overview]
Message-ID: <20261023201724.68885-1-equalizerjr@gmail.com> (raw)
In-Reply-To: <b35b82f1331141faa3603574fa3697ac@realtek.com>
Hi Ping-Ke,
Thanks for the review.
Ping-Ke Shih wrote:
> As you confirmed RTL8723DE work well, it is okay to me.
>
> Did you setup an air sniffer to capture packets? I suggest you can have
> one to check AP behavior including:
No, I have not. I only have this one RTL8723DE laptop and no second
Wi-Fi adapter that can capture in monitor mode, so I cannot check the
five points you listed over the air (beacon interval, DTIM behavior, the
TIM bit for a sleeping station, and broadcast/multicast after the
beacon).
What I did test on the RTL8723DE (kernel 7.2.5, hostapd 2.12, station
and AP on 2.4 GHz channel 1):
- With v1, the AP served a phone beside the station for about four
hours, and the station re-associated within one second each of four
times I disconnected it with the AP running.
- With the LPS PG patch, beacons of 192, 312 and 592 bytes were built
and downloaded without any "rsvd page over size" error (a 312 byte
beacon failed without it), and a 639 byte beacon was still rejected,
as calculated.
That last test only shows that the driver builds and downloads the
beacon. It does not show what is transmitted over the air.
Would you be fine with sending v2 as it is, with the commit message
stating exactly what was and was not tested? Or would you rather wait
until someone with a sniffer can run your checks? If there is a way to
check any of those points with a single adapter, I am happy to try it.
Best regards,
Carl
next prev parent reply other threads:[~2026-10-23 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 21:41 [PATCH rtw-next] wifi: rtw88: 8723d: add iface combination Carl Quist
2026-10-17 10:41 ` Luka Gejak
2026-10-17 12:40 ` Carl Quist
2026-10-19 1:59 ` Ping-Ke Shih
2026-10-23 20:17 ` Carl Quist [this message]
2026-10-25 2:38 ` Ping-Ke Shih
2026-10-25 8:29 ` Luka Gejak
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=20261023201724.68885-1-equalizerjr@gmail.com \
--to=equalizerjr@gmail.com \
--cc=linux-wireless@vger.kernel.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 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.