Phil Elwell

It doesn't help that the ancient D-Link dongle I have ignores the address change (or bdaddr ignores it).

What output do you get from the following?: ``` $ systemctl status hciuart $ systemctl status bthelper@hci0 $ systemctl status bthelper@hci1 $ systemctl status bthelper@hci2 ```

There's a bug in the bthelper script that prevents the UART-attached BT modem restriction from working. If you're feeling brave, try this patch. With your favourite editor running, edit /usr/bin/bthelper...

I'm suspicious that hci1 appears to have kept it's Pi BDADDR (b8:27:eb:xx:yy:zz) - you might have to reprogram it to something unique like 5c:f4:70:81:97:2a. hci2 looks to have a driver/firmware...

The back-port is in rpi-5.4.y now, and will be in future builds.

The `bthelper` change (along with another) will be in the next `pi-bluetooth` package, which will overwrite your patched version. Likewise, the next `raspberrypi-kernel` package will include the driver back-port, but...

File this in https://github.com/raspberrypi/linux/issues and I'll be happy to help.

Giving the timing I think you have been negatively affected by this commit: https://github.com/raspberrypi/linux/commit/3b1e49ba1a8e5853c75914eee12000aa18ada46d Unfortunately the SPI subsystem doesn't allow a default value to be specified - the maximum is...

Some application must be failing, otherwise you wouldn't know that SPI is broken. Which application is it?

Add: ``` spi.max_speed_hz = 500000 ``` after `spi.open` to restore the old default/maximum speed.