linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: linux-bluetooth@vger.kernel.org, Rocky Liao <rjliao@codeaurora.org>
Cc: bugzilla-daemon@bugzilla.kernel.org,
	jwrdegoede@fedoraproject.org, brad@pocketinnovations.com.au,
	981005@bugs.debian.org, moreno.giussani@protonmail.com,
	hui.wang@canonical.com
Subject: Re: [Bug 210681] kernel: Bluetooth: hci0: don't support firmware rome 0x31010000
Date: Sat, 13 Feb 2021 08:08:29 +0100	[thread overview]
Message-ID: <YCd67R0gtSoWCu82@eldamar.lan> (raw)
In-Reply-To: <bug-210681-62941-pQZx4HWyOB@https.bugzilla.kernel.org/>

Hi 

On Tue, Dec 29, 2020 at 10:50:10AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=210681
> 
> Bradley Jarvis (brad@pocketinnovations.com.au) changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |brad@pocketinnovations.com.
>                    |                            |au
> 
> --- Comment #10 from Bradley Jarvis (brad@pocketinnovations.com.au) ---
> Created attachment 294393
>   --> https://bugzilla.kernel.org/attachment.cgi?id=294393&action=edit
> 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

Several people have reported that since b40f58b97386 ("Bluetooth:
btusb: Add Qualcomm Bluetooth SoC WCN6855 support") they have issues
with their Bluetooth adapter stopping working. It was reported at
bugzilla[1].

Bradley Jarvis posted/attached a patch which seems to resolve the
issue, Moreno has added an alternative patch.

 [1] https://bugzilla.kernel.org/show_bug.cgi?id=210681

But there is another report at

 [2] https://bugzilla.kernel.org/show_bug.cgi?id=211571

and that last one was applied to bluetooth-next tree according to
https://lore.kernel.org/linux-bluetooth/CA2C8796-11CA-4E6F-A603-AE764516C850@holtmann.org/

Regards,
Salvatore

  reply	other threads:[~2021-02-13  7:09 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 [this message]
2020-12-30  9:15 ` bugzilla-daemon
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=YCd67R0gtSoWCu82@eldamar.lan \
    --to=carnil@debian.org \
    --cc=981005@bugs.debian.org \
    --cc=brad@pocketinnovations.com.au \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=hui.wang@canonical.com \
    --cc=jwrdegoede@fedoraproject.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=moreno.giussani@protonmail.com \
    --cc=rjliao@codeaurora.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).