On Sat, 2016-07-09 at 00:11 -0400, Jon LaBadie wrote:
On Fri, Jul 08, 2016 at 10:50:15PM +0100, Patrick O'Callaghan
wrote:
> 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:
>
Sorry, what I meant to point out (poorly), was my BT is an
internal adapter, not a dongle. Of course it could be connected
to an internal USB port.
OK. I have an internal BT adapter on my laptop, which is where I
originally used the /etc/rc.local hack.
poc