From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 214287] Bluetooth firmware rtl8671bu_fw.bin fails to load
Date: Fri, 24 Sep 2021 10:26:59 +0000 [thread overview]
Message-ID: <bug-214287-62941-JfjCeDzbdZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214287-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214287
Tadej Obrstar (tadej.obrstar@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |ANSWERED
--- Comment #1 from Tadej Obrstar (tadej.obrstar@gmail.com) ---
I finaly got some time to look into this more. After bisecting the kernel I
learned that after tripple checking the spelling I should quadruple check it
too.
I tracked the problem down to this commit:
9fd2e2949b43dea869f7fce0f8f51df44f635d59 is the first bad commit
commit 9fd2e2949b43dea869f7fce0f8f51df44f635d59
Author: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
Date: Fri May 28 17:26:44 2021 +0200
Bluetooth: btrtl: rename USB fw for RTL8761
According Realteks own BT drivers firmware RTL8761B is for UART
and RTL8761BU is for USB.
Change existing 8761B to UART and add an 8761BU entry for USB
Signed-off-by: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
So after changing the name of the firmware blob to be built into the kernel
from rtl8761b_fw.bin to rtl8761bu_fw.bin everything works again as expected.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2021-09-24 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 13:56 [Bug 214287] New: Bluetooth firmware rtl8671bu_fw.bin fails to load bugzilla-daemon
2021-09-24 10:26 ` bugzilla-daemon [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=bug-214287-62941-JfjCeDzbdZ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 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).