From: Luka Gejak <luka.gejak@linux.dev>
To: Peter Robinson <pbrobinson@gmail.com>
Cc: Ping-Ke Shih <pkshih@realtek.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Straube <straube.linux@gmail.com>,
Bitterblue Smith <rtl8821cerfe2@gmail.com>,
Hans de Goede <johannes.goede@oss.qualcomm.com>,
luka.gejak@linux.dev
Subject: Re: [PATCH v5 0/6] wifi: rtw88: preparations for RTL8723B/RTL8723BS
Date: Thu, 20 Aug 2026 17:32:36 +0200 [thread overview]
Message-ID: <2C57286A-F86B-4E47-B9A5-E9B762C25674@linux.dev> (raw)
In-Reply-To: <CALeDE9PtH3dP0gynxzA7jyJEAXjYiGU8+Q_B6Y5ehZ2K5QgjVA@mail.gmail.com>
On August 20, 2026 5:11:31 PM GMT+02:00, Peter Robinson
<pbrobinson@gmail.com> wrote:
>Hi Luka,
>
>> >> v7 follows shortly. It is hardware tested: 60 idle pings at 0% loss with
>> >> power save on, bidirectional load with no stall, 19.6 Mbit/s up and 36.8
>> >> down, UDP at 0% loss, three scans, three reconnects and a clean log.
>> >
>> >I had done some basic testing with v5, and had left a v6 to build
>> >overnight. I'll grab this shortly and do a build with v7 and do some
>> >testing.It was generally looking stable on the Pine64+ board I was
>> >using for testing.
>> >
>>
>> Thanks a lot for testing. In my testing changes in v6 and v7 didn't impact
>> performance and v7 should be as stable if not more stable then v5 and v6.
>
>I've literally just booted v7 so it'll take a bit to test it more.
>
>In v5/v6 I saw a bunch of these once it was running for a while, it
>seems to be stable though.
>
>[ 5594.434616] rtw88_8723bs mmc0:0001:1: failed to get tx report from firmware
>[ 5692.223363] rtw88_8723bs mmc0:0001:1: failed to get tx report from firmware
>[ 5747.389804] rtw88_8723bs mmc0:0001:1: failed to get tx report from firmware
>[ 5767.421101] rtw88_8723bs mmc0:0001:1: failed to get tx report from firmware
>
I think these are generic rtw88, not introduced by this driver, but I will
investigate it either way.
>Testing on iperf3 I'm getting just over 2Mbits/sec both TX/RX overall.
>
Hmm, this seems low, are those speeds on staging driver too, as in my
testing they are around 30-40 down and ~20 up.
>> >I think I may also have a device(s) with a 8723cs and/or a 8723ds I
>> >can possibly test with, I'll see if I can remember/find it over the
>> >weekend and get it running for some testing of that too.
>>
>> That would be nice, so we can see if other chips are affected, as Ping-Ke
>> said.
>
>I'll try and work out what I have over the weekend and will do some
>testing against v7 on both devices.
Thanks again.
>
>Peter
Best regards,
Luka Gejak
prev parent reply other threads:[~2026-08-20 15:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 10:53 [PATCH v5 0/6] wifi: rtw88: preparations for RTL8723B/RTL8723BS luka.gejak
2026-08-14 10:53 ` [PATCH v5 1/6] wifi: rtw88: add the RTL8723B chip type and SDIO helper luka.gejak
2026-08-14 10:53 ` [PATCH v5 2/6] wifi: rtw88: rx: mark zero length packets on RTL8723BS luka.gejak
2026-08-19 0:41 ` Ping-Ke Shih
2026-08-14 10:53 ` [PATCH v5 3/6] wifi: rtw88: tx: extend the TX report purge timeout to RTL8723BS luka.gejak
2026-08-14 10:53 ` [PATCH v5 4/6] wifi: rtw88: sdio: track free TX pages and OQT credits for RTL8723BS luka.gejak
2026-08-19 0:52 ` Ping-Ke Shih
2026-08-14 10:53 ` [PATCH v5 5/6] wifi: rtw88: sdio: set up RX aggregation and interrupts " luka.gejak
2026-08-19 0:56 ` Ping-Ke Shih
2026-08-14 10:53 ` [PATCH v5 6/6] wifi: rtw88: sdio: add TX back-pressure and retry on page starvation luka.gejak
2026-08-19 1:14 ` Ping-Ke Shih
2026-08-19 7:19 ` Luka Gejak
2026-08-19 7:31 ` Ping-Ke Shih
2026-08-19 9:17 ` Luka Gejak
2026-08-19 0:44 ` [PATCH v5 0/6] wifi: rtw88: preparations for RTL8723B/RTL8723BS Ping-Ke Shih
2026-08-19 7:19 ` [PATCH v5 0/6] wifi: rtw88: preparations for RTL8723B/RTL8723BS support Luka Gejak
2026-08-20 9:02 ` [PATCH v5 0/6] wifi: rtw88: preparations for RTL8723B/RTL8723BS Luka Gejak
2026-08-20 11:37 ` Peter Robinson
2026-08-20 14:36 ` Luka Gejak
2026-08-20 15:11 ` Peter Robinson
2026-08-20 15:32 ` Luka Gejak [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=2C57286A-F86B-4E47-B9A5-E9B762C25674@linux.dev \
--to=luka.gejak@linux.dev \
--cc=johannes.goede@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pbrobinson@gmail.com \
--cc=pkshih@realtek.com \
--cc=rtl8821cerfe2@gmail.com \
--cc=straube.linux@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