@juliank my assumption is that nothing prevents it, other than someone writing that code.
Attached is a patch for flash-kernel that will handle the compression, if needed, of kernel images for the m400. One alternate solution might be to try and copy the firmware-provided device tree data into a different memory location before loading the kernel in the boot.scr script. On one hand, that would limit the changes to code that only runs on these devices. But on the other hand, the generated uImage/uInitrd files wouldn't be usable for netbooting, as I don't think there's a way to inject memory copy commands into a config file for u-boot's pxelinux emulation. Note that we'll need to update the MAAS image generation code as well to keep that working. ** Patch added: "0001-Introduce-Boot-Kernel-Max-Size-and-support-for-compr.patch" https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1954692/+attachment/5557834/+files/0001-Introduce-Boot-Kernel-Max-Size-and-support-for-compr.patch ** Also affects: maas-images Importance: Undecided Status: New ** Changed in: flash-kernel (Ubuntu) Status: New => In Progress ** Changed in: flash-kernel (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954692 Title: Reconsider compressed kernels on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/1954692/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
