From: Ping-Ke Shih <pkshih@realtek.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: RE: EFUSE in RTW8723DS
Date: Mon, 25 Dec 2023 03:46:02 +0000 [thread overview]
Message-ID: <b73db8cd64534d329684027d40348d79@realtek.com> (raw)
In-Reply-To: <CAFBinCDD9kY-HLQXy=Ksi1QnLcOVpS0Vrnn6ksCZmTbf0MukSA@mail.gmail.com>
> -----Original Message-----
> From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> Sent: Saturday, December 23, 2023 6:40 PM
> To: Larry Finger <Larry.Finger@lwfinger.net>
> Cc: Ping-Ke Shih <pkshih@realtek.com>; linux-wireless <linux-wireless@vger.kernel.org>
> Subject: Re: EFUSE in RTW8723DS
>
> Hi Larry,
>
> apologies for my late reply.
>
> On Tue, Nov 21, 2023 at 11:47 PM Larry Finger <Larry.Finger@lwfinger.net> wrote:
> >
> >
> > Martin,
> >
> > As shown in
> > https://github.com/lwfinger/rtw88/issues/157#issuecomment-1820421821, driver
> > rtw88 shows a lot worse performance than the vendor driver for a chip with a
> > properly encoded EFUSE. Is this not a case of incorrect setting of the
> > calibration data?
> My current assumption is that the worse performance (= throughput) is
> related to the implementation in rtw88's SDIO code, not the
> programming of the RF parameters.
> I'm planning to look into this next week.
> I'd appreciate any hints from Ping-Ke on what to check / how to check
> (as long as I can do it with very basic equipment - in other words: I
> don't have an RF analyzer) :-)
>
Sorry I don't have too much idea. Basically, I would like to use a sniffer to
capture packets and compare differences between rtw89 and vendor driver, and
then check PHY rate to bisect causes.
Ping-Ke
prev parent reply other threads:[~2023-12-25 3:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 20:25 EFUSE in RTW8723DS Larry Finger
2023-11-14 0:52 ` Ping-Ke Shih
2023-11-20 19:55 ` Martin Blumenstingl
2023-11-21 22:47 ` Larry Finger
2023-12-23 10:40 ` Martin Blumenstingl
2023-12-25 3:46 ` 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=b73db8cd64534d329684027d40348d79@realtek.com \
--to=pkshih@realtek.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.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 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.