From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221754] RTL8852BE Bluetooth (0bda:b853) fails to init: Opcode 0xfcf0 failed: -16, hci0 never registers with mgmt (BD Address 00:00:00:00:00:00)
Date: Thu, 06 Aug 2026 05:01:30 +0000 [thread overview]
Message-ID: <bug-221754-62941-5o9SVnwS8r@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221754-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221754
q234rty (q23456yuiop@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |q23456yuiop@gmail.com
--- Comment #8 from q234rty (q23456yuiop@gmail.com) ---
Please do not close this bug as resolved until a fix lands in the mainline
kernel :)
In fact, support for the new firmware format has already been submitted to the
kernel:
https://lore.kernel.org/linux-bluetooth/20260624053334.3151885-1-hildawu@realtek.com/
One can verify this by pulling in the patch and simply replacing
rtl8852bu_fw.bin with the rtl8852bd_mp_chip_new.dat file extracted from the
windows driver .exe, without doing any additional processing to the .dat file.
I assume realtek intends to submit the new firmware to linux-fimware.git after
the support code has been merged into the kernel.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2026-08-06 5:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 12:10 [Bug 221754] New: RTL8852BE Bluetooth (0bda:b853) fails to init: Opcode 0xfcf0 failed: -16, hci0 never registers with mgmt (BD Address 00:00:00:00:00:00) bugzilla-daemon
2026-07-15 12:12 ` [Bug 221754] " bugzilla-daemon
2026-07-17 11:07 ` bugzilla-daemon
2026-08-02 13:01 ` bugzilla-daemon
2026-08-04 8:12 ` bugzilla-daemon
2026-08-04 11:33 ` bugzilla-daemon
2026-08-04 15:23 ` bugzilla-daemon
2026-08-04 19:35 ` bugzilla-daemon
2026-08-06 5:01 ` bugzilla-daemon [this message]
2026-08-07 16:12 ` bugzilla-daemon
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=bug-221754-62941-5o9SVnwS8r@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@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 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.