On Mon, May 18, 2026 at 4:59 AM Casey Connolly <[email protected]> wrote: > > Hi Ricardo, > > On 14/05/2026 22:57, Ricardo Salveti wrote: > > The Qualcomm default environment currently boots only with > > 'bootefi bootmgr'. This bypasses the standard boot flow used to > > discover extlinux and script boot entries, which are commonly used > > for FIT-based Linux boots. > > We intentionally don't support these alternative boot methods upstream > as they aren't standardised or supported by typical distros. There are > also plenty of inconsistencies in Linux userspace depending on if SMBIOS > (DMI data) is provide or not as well as EFI runtime services. > > Could you explain a bit more why you want to support extlinux and custom > scripts?
My main use case is for the target to automatically find and load fit images by default (based on the config used), which is a quite common use case for embedded distributions and products (see that it is also enabled by default on several other platforms in u-boot). As u-boot provides support for bootflow, supporting several mechanisms which are probed at runtime (including EFI boot), I believe it is a better default as it supports a wider range of use cases. Thanks, Ricardo
