Re: [edk2-devel] [PATCH 1/1] ArmPkg/PlatformBootManagerLib: Add path to boot UEFI Shell over UiApp

["PierreGondois" <pierre.gondois@arm.com>]

Hi Ard,
Just a ping in case this was forgotten,

Regards,
Pierre

On 4/14/23 14:45, PierreGondois via groups.io wrote:
> Hello Ard,
> 
> On 2/9/23 17:57, Ard Biesheuvel wrote:
>> On Tue, 7 Feb 2023 at 10:07, <pierre.gondois@arm.com> wrote:
>>>
>>> From: Pierre Gondois <pierre.gondois@arm.com>
>>>
>>> The UEFI Shell is a non-active boot option, at the opposite of UiApp.
>>> If no valid boot option is found, UiApp is selected. UiApp requires a
>>> human interaction. When installing a new EDKII image in CIs or when
>>> scripting is required, this is problematic.
>>>
>>> If no valid boot option is discovered, add a path to directly go to
>>> the UEFI Shell where the startup.nsh script is automatically executed.
>>> The UEFI Shell is launched after connecting possible devices, but
>>> before the reset that is meant to automatically make them visible.
>>>
>>> The new PcdUefiShellDefaultBootEnable must be set to TRUE to enable
>>> this behaviour. The Pcd is set to false by default.
>>>
>>
>> Is this similar to how we implemented this on RPi4? IIRC, a similar
>> issue came up there as well.
> 
> KvmTool, Qemu, Xen and CloudHv use the following implementation:
> PlatformBootManagerLib|ArmPkg/Library/PlatformBootManagerLib/PlatformBootManagerLib.inf
> 
> Testing:
> - using kvmtool
> - not pressing any key during the process
> I end-up in the boot menu (so not the UEFI shell).
> 
> When trying with a zero-ed flash.img, kvmtool exits with the following:
> 'PlatformBootManagerUnableToBoot: rebooting after refreshing all boot options'
> Then the flash is populated and the second attempt reaches the boot menu.
> 
> With the new PcdUefiShellDefaultBootEnable set to TRUE, we directly reach
> the UEFI shell.
> 
> Regards,
> Pierre
> 
> 
> 
> 
>