Cyril Brulebois <cy...@debamax.com> (2022-06-24): > [ Risks ] > > Since the DTB copy is not necessary in unstable/testing, it's not been > implemented in the unstable/testing package. That means that the last > CM3/CM4 DTB that would have been copied with this updated > raspi-firmware on bullseye would be left behind. I'm not sure about > the precedence (Raspberry Pi name with fallback to mainline names, or > the other way around), so it might make sense to have the > unstable/testing package get rid of those obsolete copies, to make > sure they don't get in the way. I'm not sure it (1) is required or > (2) should be a prerequisite to fixing the package in bullseye. > > After all, DTBs might vary a little over time but since they're > hardware description, we don't expect them to change dramatically.
After some more rubber ducking: even if bullseye kernels feature both CM3 and CM4 DTBs, it would make sense to guard those copies with an existence check. I'll implement that, and check that dist-upgrading between buster and bullseye works flawlessly. Regarding leftover DTBs, after upgrading from bullseye to bookworm, they should not be an issue. I'm told that upstream_kernel=1 (which we're using) should tell the bootloader to look at the mainline names, before falling back to Raspberry Pi names. Meaning current DTBs under their mainline names should have precedence over (possible) leftover DTBs under their Raspberry Pi names. I'll follow up with an updated patch once I've performed some more testing. Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
signature.asc
Description: PGP signature
