From: "Luka Gejak" <luka.gejak@linux.dev>
To: "Carl Quist" <equalizerjr@gmail.com>,
"Ping-Ke Shih" <pkshih@realtek.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH rtw-next] wifi: rtw88: 8723d: add iface combination
Date: Sat, 17 Oct 2026 12:41:16 +0200 [thread overview]
Message-ID: <DM71TCO0TBZI.1W7JBUVH0CMG7@linux.dev> (raw)
In-Reply-To: <20261016214105.255517-1-equalizerjr@gmail.com>
Hi Carl,
On Fri Oct 16, 2026 at 11:41 PM CEST, Carl Quist wrote:
> Allow 8723d to operate a station and an AP interface concurrently, using
> the combination already enabled for 8822c: one station plus one AP on the
> same channel.
>
> Without it, the AP interface cannot be brought up while the station is
> active (hostapd: "Could not set interface ap0 flags (UP): Device or
> resource busy"), so an RTL8723DE laptop cannot share its Wi-Fi
> connection.
>
> Tested on RTL8723DE [10ec:d723], firmware 48.0.0, kernel 7.2.5, with
> hostapd 2.12 on a second (AP) interface with its own MAC address:
>
> - the AP ran beside the associated station on 2.4 GHz channel 1 (HT20)
> for about four hours and served a smartphone client;
> - the AP was started and stopped repeatedly without affecting the
> station;
> - with the AP running, the station was disconnected and reconnected
> four times; it re-associated within one second each time and the AP
> stayed up.
>
> Assisted-by: LLM
> Signed-off-by: Carl Quist <equalizerjr@gmail.com>
> ---
>
> Notes:
> An AI coding assistant (Claude Opus 5.5) helped investigate this, write the
> change and run the tests above; I reviewed the change and tested it on my
> own RTL8723DE laptop.
>
> drivers/net/wireless/realtek/rtw88/main.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/realtek/rtw88/main.c b/drivers/net/wireless/realtek/rtw88/main.c
> index 0f23498..c64a3ba 100644
> --- a/drivers/net/wireless/realtek/rtw88/main.c
> +++ b/drivers/net/wireless/realtek/rtw88/main.c
> @@ -2299,7 +2299,8 @@ int rtw_register_hw(struct rtw_dev *rtwdev, struct ieee80211_hw *hw)
> hw->wiphy->max_scan_ssids = RTW_SCAN_MAX_SSIDS;
> hw->wiphy->max_scan_ie_len = rtw_get_max_scan_ie_len(rtwdev);
>
> - if (rtwdev->chip->id == RTW_CHIP_TYPE_8822C) {
> + if (rtwdev->chip->id == RTW_CHIP_TYPE_8822C ||
> + rtwdev->chip->id == RTW_CHIP_TYPE_8723D) {
> hw->wiphy->iface_combinations = rtw_iface_combs;
> hw->wiphy->n_iface_combinations = ARRAY_SIZE(rtw_iface_combs);
> }
Where does the AP beacon fit in the reserved pages?
This chip has 8 pages of 128 bytes, while rtl8822c has 16, so the 8822c
never had to squeeze a beacon in next to the station pages.
A station vif always adds five reserved packets in
rtw_add_rsvd_page_sta() and each one is counted after
rtw_fill_rsvd_page_desc() adds the 40 byte tx descriptor. Four of them
take one page, rtw_lps_pg_dpk_hdr is 169 bytes and takes two, so 6 of
the 8 pages are gone before the beacon is even considered. The beacon is
first in the list and its descriptor counts too:
total_page += rtw_len_to_page(iter->len + tx_desc_sz,
page_size);
That leaves 2 pages, so the beacon has to stay <= 216 bytes. Past that
rtw_build_rsvd_page() fails with "rsvd page over size" and
rtw_fw_download_rsvd_page() returns before rtw_download_beacon() runs.
rtw_ops_bss_info_changed() ignores the error, so hostapd thinks the AP is
up but no beacon ever reaches the firmware.
I ran this on an RTL8723DU with your patch applied. A stock hostapd WPA2
beacon came to 188 bytes and 28 bytes of extra IE still fit. At 29 bytes
the driver logged "rsvd page over size: 9" and "failed to build rsvd page
pkt" while hostapd still reported the AP as enabled. Scans still list the
SSID because probe responses go out over the normal path, so the failure
is easy to miss.
A longer SSID, WPS or a vendor IE all add bytes to the beacon, so this is
easy to reach in everyday usage.
Can the station pages be trimmed while an AP is present, or maybe this
combination should only be used on the chips with the bigger page budget?
Best regards,
Luka Gejak
next prev parent reply other threads:[~2026-10-17 10:41 UTC|newest]
Thread overview: 3+ 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 [this message]
2026-10-17 12:40 ` Carl Quist
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=DM71TCO0TBZI.1W7JBUVH0CMG7@linux.dev \
--to=luka.gejak@linux.dev \
--cc=equalizerjr@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox