From: "Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>
To: devel@edk2.groups.io, pierre.gondois@arm.com
Subject: Re: [edk2-devel] [PATCH 1/1] ArmPkg/PlatformBootManagerLib: Add path to boot UEFI Shell over UiApp
Date: Thu, 9 Feb 2023 18:14:02 +0100 [thread overview]
Message-ID: <281c6afa-6888-918c-64df-314f5b6535ca@linaro.org> (raw)
In-Reply-To: <20230207090653.395992-1-pierre.gondois@arm.com>
W dniu 7.02.2023 o 10:06, PierreGondois pisze:
> 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.
I like it. Much better option than having copy of shell.efi as
\boot\bootaa64.efi binary.
next prev parent reply other threads:[~2023-02-09 17:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 9:06 [PATCH 1/1] ArmPkg/PlatformBootManagerLib: Add path to boot UEFI Shell over UiApp PierreGondois
2023-02-09 16:57 ` Ard Biesheuvel
2023-02-13 8:39 ` PierreGondois
2023-03-31 8:47 ` PierreGondois
2023-04-14 12:22 ` [edk2-devel] " PierreGondois
2023-04-14 12:45 ` PierreGondois
[not found] ` <1755CDCBA23EBCF9.16809@groups.io>
2023-04-21 8:51 ` [edk2-devel] " PierreGondois
2023-02-09 17:14 ` Marcin Juszkiewicz [this message]
2023-02-13 14:27 ` Patrik Berglund
2023-02-14 13:36 ` Patrik Berglund
2023-04-21 14:57 ` Ard Biesheuvel
2023-04-25 6:57 ` PierreGondois
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=281c6afa-6888-918c-64df-314f5b6535ca@linaro.org \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox