From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Jes Sorensen <Jes.Sorensen@gmail.com>
Subject: RE: [PATCH rtw-next 2/3] wifi: rtl8xxxu: Dump the efuse right after reading it
Date: Tue, 14 Oct 2025 03:56:10 +0000 [thread overview]
Message-ID: <dd207e59f26842b984302e1162a9b4ad@realtek.com> (raw)
In-Reply-To: <1f544dc4-17f6-4401-995d-5cb4567b82fa@gmail.com>
Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> Someone reported a problem with their TP-Link WN722N (RTL8188EUS):
>
> usb 1-1: This Realtek USB WiFi dongle (0x2357:0x010c) is untested!
> usb 1-1: Please report results to Jes.Sorensen@gmail.com
> usb 1-1: Fatal - failed to parse EFuse
> rtl8xxxu: probe of 1-1:1.0 failed with error -22
>
> This error can happen when the first two bytes of the efuse don't have
> the expected magic value of 0x8129. In a situation like this it could
> be useful to see the contents of the efuse.
>
> Dump the efuse right after reading it, before trying to parse it.
>
> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
Reviewed-by: Ping-Ke Shih <pkshih@realtek.com>
next prev parent reply other threads:[~2025-10-14 3:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 11:52 [PATCH rtw-next 1/3] wifi: rtl8xxxu: Report the signal strength only if it's known Bitterblue Smith
2025-10-09 11:53 ` [PATCH rtw-next 2/3] wifi: rtl8xxxu: Dump the efuse right after reading it Bitterblue Smith
2025-10-14 3:56 ` Ping-Ke Shih [this message]
2025-10-09 11:55 ` [PATCH rtw-next 3/3] wifi: rtl8xxxu: Use correct power off sequence for RTL8192CU Bitterblue Smith
2025-10-14 4:23 ` Ping-Ke Shih
2025-10-14 3:54 ` [PATCH rtw-next 1/3] wifi: rtl8xxxu: Report the signal strength only if it's known Ping-Ke Shih
2025-10-21 6:59 ` Ping-Ke Shih
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=dd207e59f26842b984302e1162a9b4ad@realtek.com \
--to=pkshih@realtek.com \
--cc=Jes.Sorensen@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@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).