On Fri, 2016-07-08 at 16:31 -0400, Jon LaBadie wrote:
BTW the Broadcom BT adapter in my laptop seems to present as
a USB device:
$ lsusb
...
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation
Bus 003 Device 009: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface
Subclass)
Bus 003 Device 008: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot
Interface Subclass)
Bus 003 Device 007: ID 413c:8126 Dell Computer Corp. Wireless 355
Bluetooth
Bus 003 Device 006: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub
(part of BCM2046 Bluetooth)
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation
Yes, the Broadcom is a USB device because it's plugged into a USB port,
but still needs BT drivers for whatever is connected to it (e.g. mouse,
BT speaker, my phone etc.). The MS dongle also shows as a BT device:
$ sudo lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation
Bus 001 Device 005: ID 0a5c:2111 Broadcom Corp. ANYCOM Blue USB-UHE 200/250
Bus 001 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046
Bluetooth)
Bus 001 Device 003: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation
Bus 003 Device 003: ID 058f:3861 Alcor Micro Corp.
Bus 003 Device 002: ID 05e3:0745 Genesys Logic, Inc. Logilink CR0012
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation
but in contrast to the Broadcom the MS mouse and kb do not show up as
BT devices and don't appear to need any drivers (beyond what's in the
kernel anyway). IOW the dongle is doing some sleight of hand because it
only works specifically with those devices and AFAIK cannot be used for
general BT communication. However this is speculation.
poc