Closed CyrilBrulebois closed 2 months ago
NO GO
If we do that, we probably lose wireless support on Pi 3/Pi 4 which would get this “cleaned up” raspi-firmware
package (without firmware files) without getting the newer firmware-brcm80211
package from the Raspberry OS repository that ships the updated firmware files.
In the end it might be best to just accept having to use --force-overwrite
initially when building the Pi 5 image.
Closing this pull request for the time being.
Link: https://github.com/PiRogueToolSuite/pirogue-images/issues/2
This isn't strictly needed but would make the initial installation of
firmware-brcm80211
in the Pi 5 image case stop requiring--force-overwrite
, which would be a tad cleaner. We would also be ready to adjust if theraspi-firmware
package was upgraded in Debian 12… Indeed, that would break upgrading on the Pi 5 (trying to reinstate files “stolen” by the newerfirmware-brcm80211
package).