From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Sascha Hauer <sha@pengutronix.de>, Sean Mollet <sean@malmoset.com>
Subject: RE: [PATCH v2 1/4] wifi: rtw88: 8821cu: Fix firmware upload fail
Date: Fri, 1 Mar 2024 00:27:21 +0000 [thread overview]
Message-ID: <d87868d102754552a82c8ed99486c683@realtek.com> (raw)
In-Reply-To: <f12ed39d-28e8-4b8b-8d22-447bcf295afc@gmail.com>
> -----Original Message-----
> From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
> Sent: Friday, March 1, 2024 6:33 AM
> To: linux-wireless@vger.kernel.org
> Cc: Ping-Ke Shih <pkshih@realtek.com>; Sascha Hauer <sha@pengutronix.de>; Sean Mollet <sean@malmoset.com>
> Subject: [PATCH v2 1/4] wifi: rtw88: 8821cu: Fix firmware upload fail
>
> RTL8822CU, RTL8822BU, and RTL8821CU need an extra register write after
> reading and writing certain addresses.
>
> Without this, the firmware upload fails approximately more than 50% of
> the time.
>
> Tested with RTL8811CU (Tenda U9 V2.0) which is the same as RTL8821CU
> but without Bluetooth.
>
> Fixes: a82dfd33d123 ("wifi: rtw88: Add common USB chip support")
> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
next prev parent reply other threads:[~2024-03-01 0:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 22:32 [PATCH v2 1/4] wifi: rtw88: 8821cu: Fix firmware upload fail Bitterblue Smith
2024-02-29 22:34 ` [PATCH v2 2/4] wifi: rtw88: 8821cu: Fix connection failure Bitterblue Smith
2024-03-01 0:27 ` Ping-Ke Shih
2024-02-29 22:35 ` [PATCH v2 3/4] wifi: rtw88: 8821c: Fix beacon loss and disconnect Bitterblue Smith
2024-03-01 0:28 ` Ping-Ke Shih
2024-02-29 22:35 ` [PATCH v2 4/4] wifi: rtw88: 8821c: Fix false alarm count Bitterblue Smith
2024-03-01 0:29 ` Ping-Ke Shih
2024-03-01 0:27 ` Ping-Ke Shih [this message]
2024-03-05 17:44 ` [PATCH v2 1/4] wifi: rtw88: 8821cu: Fix firmware upload fail Kalle Valo
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=d87868d102754552a82c8ed99486c683@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@gmail.com \
--cc=sean@malmoset.com \
--cc=sha@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).