From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 210681] kernel: Bluetooth: hci0: don't support firmware rome 0x31010000
Date: Wed, 30 Dec 2020 09:15:40 +0000 [thread overview]
Message-ID: <bug-210681-62941-w4dMDGd8vU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210681-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=210681
--- Comment #11 from Antonio (antdev66@gmail.com) ---
(In reply to Bradley Jarvis from comment #10)
> Created attachment 294393 [details]
> fix hci0: don't support firmware rome error
>
> Avoid returning error code when bluetooth version match is not made from
> qca_devices_table and version high is set.
>
> This reverts an error check that was removed to support WCN6855 which does
> have the high version set. The fix is to move the check after the table is
> scanned and no version match is made.
>
> This fix will still produce the error message for example (for ATK3K
> 13d3:3402 IMC Networks Bluetooth USB Host Controller)
>
> Bluetooth: hci0: don't support firmware rome 0x1020200
>
> But the bluetooth hardware still works as it used to
I have tried it (kernel 5.10.3), I confirm that it works.
--
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:[~2020-12-30 9:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 8:50 [Bug 210681] New: kernel: Bluetooth: hci0: don't support firmware rome 0x31010000 bugzilla-daemon
2020-12-14 12:17 ` [Bug 210681] " bugzilla-daemon
2020-12-14 14:39 ` bugzilla-daemon
2020-12-14 20:07 ` bugzilla-daemon
2020-12-24 11:07 ` bugzilla-daemon
2020-12-24 13:36 ` bugzilla-daemon
2020-12-24 14:00 ` bugzilla-daemon
2020-12-24 17:00 ` bugzilla-daemon
2020-12-29 10:50 ` bugzilla-daemon
2021-02-13 7:08 ` Salvatore Bonaccorso
2020-12-30 9:15 ` bugzilla-daemon [this message]
2021-01-19 23:57 ` bugzilla-daemon
2021-01-20 15:17 ` bugzilla-daemon
2021-01-21 8:56 ` bugzilla-daemon
2021-01-22 11:28 ` bugzilla-daemon
2021-01-22 12:11 ` bugzilla-daemon
2021-01-22 13:50 ` bugzilla-daemon
2021-01-26 10:29 ` bugzilla-daemon
2021-01-26 16:52 ` bugzilla-daemon
2021-01-31 2:11 ` bugzilla-daemon
2021-01-31 14:18 ` bugzilla-daemon
2021-02-01 1:21 ` bugzilla-daemon
2021-02-13 7:04 ` bugzilla-daemon
2021-02-13 7:08 ` bugzilla-daemon
2021-02-18 13:53 ` bugzilla-daemon
2021-02-24 14:44 ` bugzilla-daemon
2021-03-02 18:40 ` 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-210681-62941-w4dMDGd8vU@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).