Hello Ard,
On 2/13/23 09:39, Pierre Gondois wrote:
Hello Ard,
On 2/9/23 17:57, Ard Biesheuvel wrote:
On Tue, 7 Feb 2023 at 10:07, <pierre.gond...@arm.com> wrote:
From: Pierre Gondois <pierre.gond...@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.
I'm not finding an equivalent for the Rpi4. I see that the
BootDiscoveryPolicy was added, but this regards which devices to connect
during boot IIUC. The UEFI Shell also seems to have been added to the
Boot Manager Menu, but this should not select the UEFI Shell by default.
Are you referring to the following ?
https://edk2.groups.io/g/devel/message/60719
If yes I don't think this patch aims to achieve the same thing.
The goal here is to reach the UEFI shell (i.e. make it an active option).
I believe the patch mentioned above doesn't modify that and is more about
making it visible in UiApp BootManager.
Please let me know if you were referring to another modification,
Regards,
Pierre
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#102253): https://edk2.groups.io/g/devel/message/102253
Mute This Topic: https://groups.io/mt/96803723/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
