From: Reto Schneider <code@reto-schneider.ch>
To: linux-firmware@kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 0/1] Updating RTL8192CU firmware
Date: Thu, 3 Sep 2020 19:57:43 +0200 [thread overview]
Message-ID: <2dcb37a5-7d55-716c-bedf-d1270700efab@reto-schneider.ch> (raw)
Message-ID: <20200903175743.ifkgdljpEVsPa68FrhZ72_qO93hM5N0k7ckZGxFqlnw@z> (raw)
In-Reply-To: <20200323225809.11594-1-code@reto-schneider.ch>
[-- Attachment #1: Type: text/plain, Size: 2386 bytes --]
On 3/23/20 11:58 PM, Reto Schneider wrote:
> Before this update, with version 80 of the firmware, the USB interface
> of the RTL8192CU WLAN controller often locked itself up:
> usb 1-2: device descriptor read/64, error -110
> usb 1-2: device not accepting address 4, error -110
> usb 1-2: device not accepting address 5, error -110
> usb usb1-port2: unable to enumerate USB device
> usb 2-2: device descriptor read/64, error -110
> usb 2-2: device descriptor read/64, error -110
>
> On ARMv5 based GARDENA smart gateway running Linux 4.19.78, this can
> be reliably reproduced by rebooting (warm) the gateway multiple times
> (max. 50 attempts needed).
> Unlike users having this issues on a USB Wi-Fi dongle, resetting of the
> chip by replugging is not an option on this gateway due to the lack of
> any power cut functionality. Therefore, a (cold) reboot of the whole
> gateway is needed.
>
> Updating the firmware of the RTL8192CU WLAN controller from version
> v80.0 to v88.2 (as per output of rtl8xxxu, which was used temporarily)
> seems to resolve this issue. The problem did no show up anymore for 1000
> restarts.
> Please note that only rtl8192cufw_TMSC.bin has been tested.
>
> Unrelated of this USB problem, another issue still remains: Using the
> rtl8192cu driver, scanning for available SSIDs yields no more results
> after a few hundred scans (iw wlan0 scan).
>
> Also, the Realtek drivers containing v88.2 of the firmware
> (v4.0.1_6911.20130308 to v4.0.9_25039.20171107) have some changes
> compared to the version v3.4.2_3727.20120404, for which I am unsure of
> whether they need to be reflected in rtl8192cu and/or rtl8xxxu.
> What I could spot for sure however, is that some tables have been
> updated:
> https://github.com/rettichschnidi/linux/commit/0c865ba26aba907b601b3b73c82111dd10e59ffe
>
> I am unsure if this changes are relevant and how the best way would be
> to ensure that this commit does not break old drivers out there.
>
> Reto Schneider (1):
> rtlwifi: v88.2 firmware files for RTL8192CU
>
> WHENCE | 6 ++++++
> rtlwifi/rtl8192cufw_A.bin | Bin 16116 -> 16126 bytes
> rtlwifi/rtl8192cufw_B.bin | Bin 16096 -> 16096 bytes
> rtlwifi/rtl8192cufw_TMSC.bin | Bin 16116 -> 16126 bytes
> 4 files changed, 6 insertions(+)
>
Is there anything left I need to do in order to get this patch merged?
Reto
[-- Attachment #2: 0xBFB93E8F422586E0.asc --]
[-- Type: application/pgp-keys, Size: 2375 bytes --]
next prev parent reply other threads:[~2020-09-03 18:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 2:45 [PATCH] rtlwifi: v88 firmware files for rtl8192cu Reto Schneider
2020-03-23 2:45 ` Reto Schneider
2020-03-23 14:57 ` Larry Finger
2020-03-23 14:57 ` Larry Finger
2020-03-23 22:58 ` [PATCH v2 0/1] Updating RTL8192CU firmware Reto Schneider
2020-03-23 22:58 ` Reto Schneider
2020-03-23 22:58 ` [PATCH v2 1/1] rtlwifi: v88.2 firmware files for RTL8192CU Reto Schneider
2020-03-23 22:58 ` Reto Schneider
2020-09-06 3:39 ` Chris Chiu
2020-09-06 3:39 ` Chris Chiu
2020-09-14 13:19 ` Josh Boyer
2020-09-20 3:00 ` Reto Schneider
2020-09-03 17:57 ` Reto Schneider [this message]
2020-09-03 17:57 ` [PATCH v2 0/1] Updating RTL8192CU firmware Reto Schneider
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=2dcb37a5-7d55-716c-bedf-d1270700efab@reto-schneider.ch \
--to=code@reto-schneider.ch \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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).