From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, ard.biesheuvel@arm.com
Cc: jon@solid-run.com
Subject: Re: [edk2-devel] [PATCH 5/5] ShellPkg: add BootManager library to add UEFI Shell menu option
Date: Wed, 27 May 2020 17:57:22 +0200 [thread overview]
Message-ID: <d90492dc-5e5c-ddc8-3b44-ebed3753a928@redhat.com> (raw)
In-Reply-To: <20200526161359.4810-6-ard.biesheuvel@arm.com>
On 05/26/20 18:13, Ard Biesheuvel wrote:
> Add a plug-in library for UiApp that creates a 'UEFI Shell' menu
> option at the root level which gives access to a form that allows
> the UEFI Shell to be launched.
>
> This gives the PlatformBootManagerLib implementation of the platform
> more flexibility in the way it handles boot options pointing to the
> UEFI Shell, which will typically be invoked with only the boot path
> connected on fast boots.
>
> This library may be incorporated to a platform build by adding a
> NULL resolution to the <LibraryClasses> section of the UiApp.inf
> {} block in the platform .DSC
>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@arm.com>
> ---
> ShellPkg/Library/ShellBootManagerLib/ShellBootManagerLib.inf | 45 ++++
> ShellPkg/Library/ShellBootManagerLib/ShellBootManagerLib.h | 44 ++++
> ShellPkg/Library/ShellBootManagerLib/ShellBootManagerLib.c | 258 ++++++++++++++++++++
> ShellPkg/Library/ShellBootManagerLib/ShellBmStrings.uni | 17 ++
> ShellPkg/Library/ShellBootManagerLib/ShellBmVfr.Vfr | 37 +++
> 5 files changed, 401 insertions(+)
I've had to go back to the blurb and re-read this part, to understand
the goal of this patch:
> - finally, add a plugin library for UiApp to expose the UEFI Shell via an
> ordinary main menu option (this works around the fact that patch #3 will
> result in the UEFI Shell disappearing from the Boot Manager list).
> Entering the shell this way will resemble the old situation, given that
> UiApp connects all devices and refreshes all boot options etc at launch.
If I understand correctly:
- patch #3 does two things: it clears LOAD_OPTION_ACTIVE (preventing the
boot manager from auto-booting the shell), and sets LOAD_OPTION_HIDDEN
(hiding the boot option from UiApp),
- patch #5 undoes LOAD_OPTION_HIDDEN, in effect -- it makes sure that we
still see the shell option "somewhere" in UiApp (not among the boot
options, but at the root level)
Can we:
- drop patch#5, and
- pass zero (0) as "Attributes" to PlatformRegisterFvBootOption() in
patch#3, rather than LOAD_OPTION_HIDDEN?
Because, per spec, Attributes=0 should prevent the auto-booting of the
shell *without* hiding the shell boot option from the menu.
Thanks,
Laszlo
next prev parent reply other threads:[~2020-05-27 15:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 16:13 [PATCH 0/5] ArmPkg/PlatformBootManagerLib: play nice without ConnectAll() Ard Biesheuvel
2020-05-26 16:13 ` [PATCH 1/5] ArmPkg/PlatformBootManagerLib: register 's' as UEFI Shell hotkey Ard Biesheuvel
2020-05-27 15:24 ` [edk2-devel] " Laszlo Ersek
2020-05-26 16:13 ` [PATCH 2/5] ArmPkg/PlatformBootManagerLib: fall back to the UiApp on boot failure Ard Biesheuvel
2020-05-26 21:24 ` [edk2-devel] " Leif Lindholm
2020-05-27 15:34 ` Laszlo Ersek
2020-05-27 17:39 ` Leif Lindholm
2020-05-27 15:25 ` Laszlo Ersek
2020-05-26 16:13 ` [PATCH 3/5] ArmPkg/PlatformBootManagerLib: hide UEFI Shell as a regular boot option Ard Biesheuvel
2020-05-26 21:27 ` [edk2-devel] " Leif Lindholm
2020-05-27 15:40 ` Laszlo Ersek
2020-05-26 16:13 ` [PATCH 4/5] ArmPkg/PlatformBootManagerLib: don't connect all devices on each boot Ard Biesheuvel
2020-05-27 15:49 ` [edk2-devel] " Laszlo Ersek
2020-05-26 16:13 ` [PATCH 5/5] ShellPkg: add BootManager library to add UEFI Shell menu option Ard Biesheuvel
2020-05-27 15:57 ` Laszlo Ersek [this message]
2020-05-27 17:22 ` [edk2-devel] " Ard Biesheuvel
2020-05-28 19:55 ` Laszlo Ersek
2020-05-26 22:01 ` [PATCH 0/5] ArmPkg/PlatformBootManagerLib: play nice without ConnectAll() Leif Lindholm
2020-05-27 5:35 ` [edk2-devel] " Ard Biesheuvel
2020-05-27 10:43 ` Leif Lindholm
2020-05-27 10:50 ` Ard Biesheuvel
2020-05-27 13:41 ` Leif Lindholm
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=d90492dc-5e5c-ddc8-3b44-ebed3753a928@redhat.com \
--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