From: ValdikSS <iam@valdikss.org.ru>
To: Sascha Hauer <s.hauer@pengutronix.de>,
linux-wireless <linux-wireless@vger.kernel.org>
Cc: Hans Ulli Kroll <linux@ulli-kroll.de>,
Larry Finger <Larry.Finger@lwfinger.net>,
Pkshih <pkshih@realtek.com>, Tim K <tpkuester@gmail.com>,
Nick Morrow <morrownr@gmail.com>,
Viktor Petrenko <g0000ga@gmail.com>,
Andreas Henriksson <andreas@fatal.se>,
kernel@pengutronix.de, stable@vger.kernel.org,
"Alex G." <mr.nuke.me@gmail.com>
Subject: Re: [PATCH 0/2] RTW88 USB bug fixes
Date: Sat, 1 Apr 2023 05:08:59 +0300 [thread overview]
Message-ID: <57d3052f-a38f-c45b-bc3f-aa8ebfd7188e@valdikss.org.ru> (raw)
In-Reply-To: <317782bf-b12a-b6b8-8f08-5e4e19f3b309@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 701 bytes --]
On 31.03.2023 23:34, Alex G. wrote:
> On 3/31/23 07:10, Sascha Hauer wrote:
>> This series fixes two bugs in the RTW88 USB driver I was reported from
>> several people and that I also encountered myself.
>>
>> The first one resulted in "timed out to flush queue 3" messages from the
>> driver and sometimes a complete stall of the TX queues.
>>
>> The second one is specific to the RTW8821CU chipset. Here 2GHz networks
>> were hardly seen and impossible to connect to. This goes down to
>> misinterpreting the rfe_option field in the efuse.
Tested on RTL8811CU, these two patches fix both issues. 2.4 GHz networks
now work perfectly fine.
Tested-by: ValdikSS <iam@valdikss.org.ru>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2023-04-01 2:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 12:10 [PATCH 0/2] RTW88 USB bug fixes Sascha Hauer
2023-03-31 12:10 ` [PATCH 1/2] wifi: rtw88: usb: fix priority queue to endpoint mapping Sascha Hauer
2023-03-31 14:31 ` Jonathan Bither
2023-04-04 7:11 ` Sascha Hauer
2023-03-31 12:10 ` [PATCH 2/2] wifi: rtw88: rtw8821c: Fix rfe_option field width Sascha Hauer
2023-03-31 13:16 ` Greg KH
2023-03-31 20:34 ` [PATCH 0/2] RTW88 USB bug fixes Alex G.
2023-04-01 2:05 ` Larry Finger
2023-04-01 2:08 ` ValdikSS [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=57d3052f-a38f-c45b-bc3f-aa8ebfd7188e@valdikss.org.ru \
--to=iam@valdikss.org.ru \
--cc=Larry.Finger@lwfinger.net \
--cc=andreas@fatal.se \
--cc=g0000ga@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@ulli-kroll.de \
--cc=morrownr@gmail.com \
--cc=mr.nuke.me@gmail.com \
--cc=pkshih@realtek.com \
--cc=s.hauer@pengutronix.de \
--cc=stable@vger.kernel.org \
--cc=tpkuester@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;
as well as URLs for NNTP newsgroup(s).