https://bugzilla.kernel.org/show_bug.cgi?id=78621 Johan Hedberg <johan.hedberg@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |johan.hedberg@xxxxxxxxx --- Comment #2 from Johan Hedberg <johan.hedberg@xxxxxxxxx> --- I doubt the issue applies to all Broadcom adapters since those are probably the most common ones on the market. I've got several of them and they all work fine. Here's a decoded snippet (using btmon instead of hcidump) from the provided HCI log: < HCI Command: Read Local Version Information (0x04|0x0001) plen 0 0.316895 > HCI Event: Command Complete (0x0e) plen 12 0.319876 Read Local Version Information (0x04|0x0001) ncmd 1 Status: Success (0x00) HCI version: Bluetooth 1.2 (0x02) - Revision 3 (0x0003) LMP version: Bluetooth 1.2 (0x02) - Subversion 2048 (0x0800) Manufacturer: Broadcom Corporation (15) < HCI Command: Read BD ADDR (0x04|0x0009) plen 0 0.319905 > HCI Event: Command Complete (0x0e) plen 10 0.321874 Read BD ADDR (0x04|0x0009) ncmd 1 Status: Success (0x00) Address: 00:0D:3A:A8:0B:BE (Microsoft Corp.) What's interesting is that the adapter is using an address allocated to Microsoft, which leads me to wonder whether this is an authentic Broadcom device or not (we've seen before cheap Asian manufacturers having similar inconsistencies in manufacturer information). If this is a USB device could you also provide the USB id, etc for it. Usually the relevant part from the output of the usb-devices command is enough. This would allow us to make a very specific quirk for this piece of hardware. -- You are receiving this mail because: You are the assignee for the bug. -- 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
