From: Marcel Holtmann <marcel@holtmann.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
Linux Bluetooth mailing list <linux-bluetooth@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Atheros 1525/QCA6174 BT issue
Date: Thu, 8 Mar 2018 10:06:51 +0100 [thread overview]
Message-ID: <184DA6FB-F23C-4C37-B89B-FE865DC9731C@holtmann.org> (raw)
In-Reply-To: <s5hd10fkm49.wl-tiwai@suse.de>
Hi Takashi,
> we've got a but report about the broken Atheros BT on the recent
> kernels:
> http://bugzilla.opensuse.org/show_bug.cgi?id=1082504
>
> In short, btusb can't load the patch ar3k/AthrBT_0x00000200.dfu, and
> this could be worked around by the patch to move 0cf3:3004 blacklist
> entry to use BTUSB_QCA_ROM instead of BTUSB_ATH3012.
>
> And this looks like a long-standing problem, at least for over two
> years. Many web pages suggest the same patch, but it's never merged
> to upstream.
>
> So this made me wonder what's going on. I see that the BTUSB_ATH3012
> quirk was originally introduced just for this chip id (0cf3:3004).
> Is it a different variant from the original chip that causes a
> problem?
not all patches from distro kernel are sent upstream. I have not heard of this specific issues, but happy to accept patches to get it fixed.
Regards
Marcel
next prev parent reply other threads:[~2018-03-08 9:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 8:27 Atheros 1525/QCA6174 BT issue Takashi Iwai
2018-03-08 9:06 ` Marcel Holtmann [this message]
2018-03-08 9:16 ` Takashi Iwai
2018-03-13 8:05 ` Takashi Iwai
2018-03-13 8:10 ` Marcel Holtmann
2018-03-13 8:32 ` Takashi Iwai
2018-03-13 8:38 ` Marcel Holtmann
2018-03-13 8:50 ` Takashi Iwai
2018-03-13 9:15 ` Marcel Holtmann
2018-03-15 15:56 ` Takashi Iwai
2018-03-15 18:32 ` Marcel Holtmann
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=184DA6FB-F23C-4C37-B89B-FE865DC9731C@holtmann.org \
--to=marcel@holtmann.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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.