From: Ping-Ke Shih <pkshih@realtek.com>
To: Luka Gejak <luka.gejak@linux.dev>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH rtw-next v2 1/2] wifi: rtw88: move the bmc high queue decision to tx.c
Date: Tue, 27 Oct 2026 01:19:49 +0000 [thread overview]
Message-ID: <d6af5cebfa1a46e2bc2da662634766d7@realtek.com> (raw)
In-Reply-To: <eaaa18cd9f23a3731bd1f8f17eb0885d1a17049f@linux.dev>
Luka Gejak <luka.gejak@linux.dev> wrote:
> October 25, 2026 at 3:49 AM, "Ping-Ke Shih" <pkshih@realtek.com> wrote:
> >
> > Luka Gejak <luka.gejak@linux.dev> wrote:
> >
> > >
> > > I was thinking, as staging got removed, for 10-ish weeks(until 7.5)
> > > users of RTL8723BS won't have AP mode. So I was wondering if these two
> > > patches could pass as fixes into rc2 release(or whatever is the first
> > > rc into which rtw tree is merged), as this would be DHCP stall fix. To
> > > elaborate: when this driver was merged it, was exposingAP mode to
> > > userspace, due to RTW88 doing it globally. Therefore AP mode existed,
> > > but wasn't working properly. So maybe it's a bit of a stretch, but I
> > > think it's a valid proposal to send it as a fix into next rc release.
> > >
> > Did you think people use staging driver with AP mode?
>
> It appears so. I saw on forums and articles about the new driver that
> some people were complaining because only station mode is working
> because they exclusively or mostly use it as an AP point.
This lets me think if I merge RTL8723BS to rtw88 and delete rtl8723bs
from staging too early. The staging rtl8723bs is a vendor driver which
mostly implements "full" functions, but rtw88 should be not. To smoothly
migrate from staging to rtw88, we should implement equivalent functions
before merging, at least functions people are using.
But I really don't want to go back to staging driver. Let's pick the
fixes of AP mode. I hope no more functions needed to be picked.
>
> >
> > Personally, I want this goes to rtw-next, but if you have strong opinion
> > that people need this. I can pick them and let it goes to -rc.
>
> I think it would be better to pick these into rc, especially since
> the feature exists right now but is broken.
Comparing to staging rtl8723bs, it might be seen as broken, but for rtw88
I consider this as a new feature.
Ping-Ke
prev parent reply other threads:[~2026-10-27 1:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 12:43 [PATCH rtw-next v2 1/2] wifi: rtw88: move the bmc high queue decision to tx.c Luka Gejak
2026-10-21 12:43 ` [PATCH rtw-next v2 2/2] wifi: rtw88: sdio: limit the high queue to DTIM delivery Luka Gejak
2026-10-22 2:24 ` Ping-Ke Shih
2026-10-22 4:30 ` Luka Gejak
2026-10-22 4:33 ` Ping-Ke Shih
2026-10-22 2:20 ` [PATCH rtw-next v2 1/2] wifi: rtw88: move the bmc high queue decision to tx.c Ping-Ke Shih
2026-10-22 5:11 ` Luka Gejak
2026-10-23 21:34 ` Luka Gejak
2026-10-25 2:49 ` Ping-Ke Shih
2026-10-25 8:26 ` Luka Gejak
2026-10-27 1:19 ` 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=d6af5cebfa1a46e2bc2da662634766d7@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
/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