> [X.] Other notes, patches, fixes, workarounds:
>
> A workaround to this bug is to blacklist ath3k and btusb, and have two versions of them:
>
> 1) The patched versions, which contains the following lines:
>
> in btusb.c:
> { USB_DEVICE(0x04CA, 0x300d) },
>
> in ath3k.c:
> { USB_DEVICE(0x04ca, 0x300d), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x04ca, 0x300d), .driver_info = BTUSB_ATH3012 },
> 2) The unpatched versions, same modules without these lines.
>
> The workaround is to insmod the patched versions (which load the
> firmware), rmmod them after a second, and insmod the unpatched versions.
> After that Bluetooth is working until next computer suspend or halt.
> The firmware is not kept loaded after suspend or halt, but it is kept
> loaded after a reboot. Using the unpatched versions without the firmware being loaded makes Bluetooth look activated but unusable.
>
> I also noticed that iProduct = 0 for the 04ca:300d device.
>
> This is my first bug report to the kernel, so please tell me if I did anything wrong.
>
> Cheers,
>
> Raphaël.
>
This looks like a bug in ath3k module. It loads firmware, but after that hangs.
That is why when you load btusb after that, BT works.
iProduct is 0 for all new AR3012 devices. It is not a criterion now to distinguish AR3011 and AR3012.
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
