On Tue, Jul 14, 2015 at 10:58:50PM +0200, Marcel Holtmann wrote: > Hi Chris, > > >>>> Actually can you run something like "hciconfig hci0 version" and see > >>>> if it really is a Broadcom chip in there or if Apple switched vendors > >>>> and we are accidentally assuming it is Broadcom while in reality it is > >>>> not. If it is not then the quirk might actually not apply either > >>>> anymore. > >>> > >>> mason@ret ~> hciconfig hci0 version > >>> hci0: Type: BR/EDR Bus: USB > >>> BD Address: 60:03:08:8D:0D:A9 ACL MTU: 1021:8 SCO MTU: 64:1 > >>> HCI Version: 4.0 (0x6) Revision: 0x21ae > >>> LMP Version: 4.0 (0x6) Subversion: 0x414e > >>> Manufacturer: Broadcom Corporation (15) > >> > >> so it is a Broadcom. What MacBook is this anyway? > > > > macbookpro 13" from 2013 (newer model in '13) > > besides having that Bluetooth module for testing, I also have that actual Macbook. And I did test this. It worked fine for me. Maybe some OS X update messed with the firmware. Worth while checking. This only runs linux, I don't dual boot. -chris -- 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
