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? > > Switch do_boot to 'bootflow scan -lb' so bootstd handles boot method > selection. This keeps EFI support available through the EFI boot > methods while also enabling extlinux/boot.scr based bootflows by > default. > > Signed-off-by: Ricardo Salveti <[email protected]> > --- > board/qualcomm/default.env | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/board/qualcomm/default.env b/board/qualcomm/default.env > index dbf6f4e7260..a47c289acce 100644 > --- a/board/qualcomm/default.env > +++ b/board/qualcomm/default.env > @@ -3,7 +3,7 @@ stdout=serial,vidconsole > stderr=serial,vidconsole > preboot=scsi scan; usb start > fastboot=fastboot -l $fastboot_addr_r usb 0 > -do_boot=bootefi bootmgr > +do_boot=bootflow scan -lb > bootmenu_0=Boot first available device=run do_boot > bootmenu_1=Enable fastboot mode=run fastboot > bootmenu_2=Reset device=reset -- // Casey (she/her)
