@chih: Was helping a user in #ubuntu today with the same device ID (413c:8143). But I think I'm a bit confused by this, I'm looking at the upstream source and I see:
I don't see 0x8143 product Id listed as a matching USB device? So even if a user were to have the correct firmware in place (the user on #ubuntu did, afaict), btusb won't match. Is this really an upstream bug?
@chih: Was helping a user in #ubuntu today with the same device ID (413c:8143). But I think I'm a bit confused by this, I'm looking at the upstream source and I see:
$ grep 413c drivers/ bluetooth/ btusb.c
{ USB_DEVICE(0x413c, 0x8197) },
{ USB_DEVICE(0x413c, 0x8126), .driver_info = BTUSB_WRONG_SCO_MTU },
{ USB_DEVICE(0x413c, 0x8152), .driver_info = BTUSB_WRONG_SCO_MTU },
{ USB_DEVICE(0x413c, 0x8156), .driver_info = BTUSB_WRONG_SCO_MTU },
I don't see 0x8143 product Id listed as a matching USB device? So even if a user were to have the correct firmware in place (the user on #ubuntu did, afaict), btusb won't match. Is this really an upstream bug?
Thanks,
Nish