Hi,
I have a OQO Model 01+[1] that, for whatever reason, has had the USB ID's
of it's internal wireless and bluetooth altered to a OQO specific product
id. However adding the Vendor/Product ID with the following patch to
kernel version 2.6.25.6:-
--- linux-2.6.25.6.orig/drivers/bluetooth/hci_usb.c 2008-04-17
03:49:44.000000000 +0100
+++ linux-2.6.25.6/drivers/bluetooth/hci_usb.c 2008-06-20
19:48:51.000000000 +0100
@@ -98,6 +98,9 @@
/* Canyon CN-BTU1 with HID interfaces */
{ USB_DEVICE(0x0c10, 0x0000), .driver_info = HCI_RESET },
+ /* OQO Model 01+ internal Bluetooth */
+ { USB_DEVICE(0x1557, 0x0003) },
+
{ } /* Terminating entry */
};
Results in working bluetooth. I can scan using hcitool and have
transfered files to/from my mobile phone with success. Are there any
other tests I should run, or shall I submit the above as a formal patch?
According to this forum post[2] it is actually a CSR chipset. I haven't
opened my device to confirm this, but my lsusb output is available
here[3].
Many thanks for all your work,
[1] http://en.wikipedia.org/wiki/OQO#OQO_Model_01_.26_01.2B
(the OQO site doesn't seem to have a product description anymore)
[2] http://www.oqotalk.com/index.php/topic,10.0.html#msg435
[3] http://jamie.lentin.co.uk/hardware/oqo_01plus/lsusb.txt
--
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
