Hi all,
drivers/bluetooth/btusb.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 55ac349..07622141a 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -101,6 +101,7 @@ static struct usb_device_id btusb_table[] = {
{ USB_DEVICE(0x0c10, 0x0000) },
/* Broadcom BCM20702A0 */
+ { USB_DEVICE(0x0489, 0xe031) },
{ USB_DEVICE(0x0a5c, 0x21e3) },
{ USB_DEVICE(0x413c, 0x8197) },
I fear this alone won't be enough. We are discussing this topic here:
https://bbs.archlinux.org/viewtopic.php?pid=1038521#p1038521
Short summary:
The adapter seems to work in first but the log files say:
'localhost bluetoothd[1718]: Inquiry Failed with status 0x12'
while scanning.
From a short look in the Windows inf. file:
Fujitsu is listed there in a separate section called RAMUSBE031. There
is also this "BCM20702A0_001.001.024.0023.0055.hex" file copied along
with the driver, which is then referenced in the registry as
"RAMPatchFileName". There is a long list of other 20702 adapters divided
in those that need a 'RAM patch' or not. Maybe you could complete your
list of compatible devices bases on this.
I own one of these Fujitsu laptops (E751 0x0489:0xe031) with the need
for the hex file. If you want me to I can do more testing with to your
guidance.
Thanks for your attention
Harvey
--
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
