On Tue, 19 Aug 2025 at 16:35, Tom Rini <tr...@konsulko.com> wrote: > > On Tue, Aug 19, 2025 at 04:33:07PM +0100, Peter Robinson wrote: > > On Tue, 19 Aug 2025 at 15:57, Tom Rini <tr...@konsulko.com> wrote: > > > > > > On Tue, Aug 19, 2025 at 12:13:31PM +0100, Peter Robinson wrote: > > > > On Mon, 18 Aug 2025 at 17:51, Tom Rini <tr...@konsulko.com> wrote: > > > > > > > > > > At this time there are still major Linux distributions which by > > > > > default > > > > > boot using LEGACY_IMAGE_FORMAT type scripts. Add this option to > > > > > DISTRO_DEFAULTS to ensure these platforms can still boot. > > > > > > > > What is the legacy image format exactly? Does select make it non > > > > optional, can we use imply or similar here? > > > > > > In this case "legacy image format" is uImage-style images, rather than > > > FIT images. And no, we can't imply it because then we'd break Debian > > > (which doesn't boot on a handful of platforms now which do have > > > DISTRO_DEFAULTS but don't have this). > > > > The distro boot stuff, which if my memory servers, is what the > > DISTRO_DEFAULTS is used for, never used the uImage style kernels. > > The same uImage-style header is what's on top of a "boot.scr" type file.
The distro default scripts never used that either, the whole point of them was to move away from manually crafted scripts and custom formats to boot a device.
