@mbirth One thing has just occurred to me: at some point in the future you may have to switch to using u-boot or implement a workaround, at least for 64-bit builds...
The reason is that at the moment our 64-bit kernels are uncompressed because the Linux kernel doesn't support self-extracting on arm64 (and apparently won't any time soon - compression is seen as something bootloaders ought to be handling). We'd obviously like to have compressed kernels (it speeds up the boot sequence and saves space on the relatively small boot partition) and to that end I recently updated our u-boot script on Classic to detect a gzipped kernel and handle de- compressing it before launching it. However, the kernel builds haven't yet been switched to be compressed as Core's boot also needs updating first. Anyway, I don't *think* the Pi's bootloader is capable of dealing with compressed kernel images in which case, when we do start compressing our kernels, I'm afraid your boot sequence will suddenly break. It'll be pretty trivial to work around (just gunzip the kernel image on /boot) but it's something you should be aware of! This won't affect armhf images which currently use self-extracting compressed images (and will continue do so for the foreseeable future). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847163 Title: [FFe] Firmware bump for Pi 4 boot support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1847163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
