Bluetooth Device
USB ID 0a12:1010 · Cambridge Silicon Radio, Ltd
| Vendor | Cambridge Silicon Radio, Ltd |
|---|---|
| Vendor ID | 0a12 |
| Device ID | 1010 |
| Windows hardware ID | USB\VID_0A12&PID_1010 |
| Linux modalias | usb:v0A12p1010 |
| Linux driver | no driver with exact ID |
Frequently asked questions
Which device has USB ID 0a12:1010?
USB ID 0a12:1010 is “Bluetooth Device” made by Cambridge Silicon Radio, Ltd (vendor ID 0a12, device ID 1010).
Which Linux driver supports Bluetooth Device?
Linux kernel 6.12 lists no driver for this exact ID. Most USB devices (keyboards, mice, storage, webcams, audio) still work through generic class drivers such as usbhid, usb-storage, uvcvideo or snd-usb-audio. Overview of device classes and their drivers
How do I check whether Bluetooth Device is in my computer?
On Linux, lsusb -d 0a12:1010 shows the device if it is present. On Windows, open Device Manager, then Properties → Details → Hardware Ids; it appears as USB\VID_0A12&PID_1010.
How do I see which driver is currently in use?
lsusb -t prints the device tree with the bound driver (Driver=…) for each interface.
Nearby entries
- 0101 – Casira with BlueCore2-Flash Module
- 0102 – Casira with BlueCore3-Multimedia Module
- 0103 – Casira with BlueCore3-Flash Module
- 0104 – Casira with BlueCore4-External Module
- 0105 – Casira with BlueCore4-Multimedia Module
- 1000 – Bluetooth Dongle (HID proxy mode)
- 1011 – Bluetooth Device
- 1012 – Bluetooth Device
- 1243 – CSRA64210 [TaoTronics Headset BH-22 in charging mode]
- 4007 – Mpow HC5 Headset in charging mode - HID / Mass Storage
- 4010 – Mpow HC5 Headset in charging mode - USB Hub
- ffff – USB Bluetooth Device in DFU State