Remove Bluetooth firmware

[Juerg Haefliger]

Raspberry Pi Bluetooth firmware is now provided by the bluez-firmware package (1.2-11ubuntu1). The blobs are compressed so there's no file namespace collision. Please remove the following BT blobs and links from linux-firmware-raspi:

-rw-r--r-- 1 root root 30049 Aug 25 2023 /lib/firmware/brcm/BCM43430A1.hcd
lrwxrwxrwx 1 root root 14 Aug 25 2023 /lib/firmware/brcm/BCM43430A1.raspberrypi,model-zero-2-w.hcd -> BCM43430A1.hcd
-rw-r--r-- 1 root root 44376 Aug 25 2023 /lib/firmware/brcm/BCM43430B0.hcd
lrwxrwxrwx 1 root root 14 Aug 25 2023 /lib/firmware/brcm/BCM43430B0.raspberrypi,model-zero-2-w.hcd -> BCM43430B0.hcd
-rw-r--r-- 1 root root 63806 Aug 25 2023 /lib/firmware/brcm/BCM4345C0.hcd
-rw-r--r-- 1 root root 49610 Aug 25 2023 /lib/firmware/brcm/BCM4345C5.hcd

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Dave Jones (waveform)]

Argh, unfortunately the situation is a little more complicated than it seems. Upstream (in RaspiOS):

 * BCM4345C5 has now been updated so it's a newer version than that in bluez-firmware
 * BCM43430B0 is renamed to SYN43430B0 (presumably as a result of broadcom assets changing hands to synaptics)
 * BCM43430A1 has disappeared (in favour of the bluez-firmware), and
 * BCM4343A2 is a newly added firmware, presumably for some future iteration of one of the Pis

Still, bluez-firmware is specifically tagged as being for "Raspberry Pi hardware" and it does currently conflict with linux-firmware-raspi, which is a Bad Thing (tm). So ... what should *probably* happen is for the updates to the Raspberry Pi Bluetooth firmware listed above, to be moved into bluez-firmware, and for the pi-bluetooth package to be updated to depend on bluez-firmware instead of linux-firmware-raspi.

However, pi-bluetooth is seeded on the Pi Desktop images (because Bluetooth is expected to work OOTB on the desktop). linux-firmware-raspi is currently in restricted, but bluez-firmware is in multiverse, so moving these firmwares is going to cause a component mismatch which will require an MIR on bluez-firmware to sort out. Given we're already passed feature freeze, I'm not confident in getting an MIR through the process before the beta (when we need to have images produced) on the 4th April.

So, assigning myself to this, but I'll be putting this off until 24.10. For the time being, I'll bump the bluetooth firmwares in linux-firmware-raspi as usual, and add a Conflicts on bluez-firmware to linux-firmware-raspi to ensure people can't try and install them simultaneously.

[Juerg Haefliger (juergh)]

Oh, that sounds bad. When you say 'it does currently conflict with linux-firmware-raspi' you mean a conflict in functionality? They are co-installable. What is 'require an MIR on bluez-firmware to sort out'? It seems the easiest/correct is indeed for pi-bluetooth to depend on bluez-firmware. Or I'll upload a new bluez-firmware with the changes reverted. Sigh. Sorry for the late mess.