>>>> we've got a but report about the broken Atheros BT on the recent
>>>> 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
>>> 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.
>> OK, basically it's like below.
>> But, as mentioned, this made me wonder whether it's the right fix.
>> The BTUSB_ATH3012 quirk was introduced exactly for this chip ID
>> (0cf3:3004), and now this chip is moved to another quirk...
>> If this is the right move, I can re-submit via git-send-email, too.
>> Just let me know.
> Marcel, could you take a look at this?
> If it sucks, let's seek for a better solution.
wasn’t the confusion that this is fixed with a recent kernel? I am lost in this
thread. I mean if people add Tested-by, then I can take this as well. Otherwise
we might need someone from Qualcomm to shed some light into these.