From: Ping-Ke Shih <pkshih@realtek.com>
To: "hi@shreyan.sh" <hi@shreyan.sh>, Jes Sorensen <Jes.Sorensen@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtl8xxxu: Enable AP mode for RTL8188EU
Date: Sun, 1 Nov 2026 04:10:23 +0000 [thread overview]
Message-ID: <81c3d0056a0849078715e0f0be074d1e@realtek.com> (raw)
In-Reply-To: <1381CC32-E73C-483E-8F64-27EDE6AE8E6E@shreyan.sh>
hi@shreyan.sh <hi@shreyan.sh> wrote:
> From 0a3cdd4c6cc416804e49c935516a22e854a87483 Mon Sep 17 00:00:00 2001
> From: Shreyansh Khajanchi <hi@shreyan.sh>
> Date: Fri, 30 Oct 2026 12:34:44 +0530
> Subject: [PATCH] wifi: rtl8xxxu: Enable AP mode for RTL8188EU
>
> The RTL8188EU shares the AP mode implementation in core.c with the
> other chips supported by this driver, so advertising
> NL80211_IFTYPE_AP is enough to make it usable as an access point.
>
> Set max_macid_num to 32 as well, so that max_ap_assoc_sta is
> initialised. The vendor driver defines NUM_STA as 32, and starts
> station MAC IDs at 2 because 0 and 1 are reserved for
> broadcast/multicast. This matches RTL8192CU, which also sets
> max_macid_num to 32.
Do you have a sniffer to have air capture to check beacon?
If so, please check TIM for unicast packets if station goes
sleepy, and TIM for broadcast/multicast packets (for example,
send a broadcast ARP by ping a non-existing IP).
>
> Tested with an RTL8188EUS (0bda:8179) on a Raspberry Pi Zero running
> 6.12 (armv6): hostapd serves a 2.4 GHz WPA2 network, clients associate
> and pass traffic.
>
> Signed-off-by: Shreyansh Khajanchi <hi@shreyan.sh>
I give my reviewed-by, but still want test results of TIM.
Reviewed-by: Ping-Ke Shih <pkshih@realtek.com>
next prev parent reply other threads:[~2026-11-01 4:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 7:35 [PATCH] wifi: rtl8xxxu: Enable AP mode for RTL8188EU hi
2026-11-01 4:10 ` Ping-Ke Shih [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-12 14:21 Georg Müller
2026-03-12 14:29 ` Georg Müller
2026-03-12 15:58 ` Bitterblue Smith
2026-03-12 16:08 ` Georg Müller
2026-03-12 17:06 ` Bitterblue Smith
2026-03-12 22:20 ` Bitterblue Smith
2026-03-12 23:52 ` Georg Müller
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=81c3d0056a0849078715e0f0be074d1e@realtek.com \
--to=pkshih@realtek.com \
--cc=Jes.Sorensen@gmail.com \
--cc=hi@shreyan.sh \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox