Hi Floris, > When using newer upstream Linux kernels on Raspberry Pi 3+ that have the brcm,bcm43438-bt serial slave device-tree entries, all devices get the same BD address 43:45:C0:00:1F:AC. > > What is the recommend way of fixing that up nowadays? > > The vendor's standard start-up script makes up a BD address derived from SoC serial number, and pass that as parameter to hciattach. > But that doesn't work when the kernel is managing the hci connection instead. > And cannot find any device-tree parameter to pass address either. is it actually loading the Bluetooth firmware for the RPi since once that is loaded the address should be configured correctly. Or is the RPi 3+ different in this regard? If this is really always the same address with the correct firmware loaded, then the driver needs to set the QUIRK_INVALID_BDADDR to indicate that the device is missing the address configuration. Regards Marcel
