From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 0/3] efi_loader: setting boot device
Date: Tue, 12 Jan 2021 20:58:39 +0100 [thread overview]
Message-ID: <20210112195842.252946-1-xypron.glpk@gmx.de> (raw)
Up to now the bootefi command uses the last file loaded to determine the
boot partition. This has led to user irritation when the fdt has been
loaded from another partition after the EFI binary.
Before setting the boot device from a loaded file check if it is a PE-COFF
image.
The first patch carves out the test function.
The second make use of the PE-COFF check.
The third add the display of the boot device and file path for easier testing.
Heinrich Schuchardt (3):
efi_loader: print boot device and file path in helloworld
efi_loader: carve out efi_check_pe()
efi_loader: setting boot device
cmd/bootefi.c | 14 ++-
doc/uefi/uefi.rst | 11 +-
fs/fs.c | 3 +-
include/efi_loader.h | 8 +-
lib/efi_loader/efi_image_loader.c | 80 ++++++++------
lib/efi_loader/helloworld.c | 167 ++++++++++++++++++++++++------
net/tftp.c | 9 +-
7 files changed, 211 insertions(+), 81 deletions(-)
--
2.29.2
next reply other threads:[~2021-01-12 19:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 19:58 Heinrich Schuchardt [this message]
2021-01-12 19:58 ` [PATCH 1/3] efi_loader: print boot device and file path in helloworld Heinrich Schuchardt
2021-01-14 15:42 ` Simon Glass
2021-01-15 1:56 ` AKASHI Takahiro
2021-01-15 3:12 ` Heinrich Schuchardt
2021-01-15 4:29 ` AKASHI Takahiro
2021-01-15 12:02 ` Heinrich Schuchardt
2021-01-18 1:38 ` AKASHI Takahiro
2021-01-12 19:58 ` [PATCH 2/3] efi_loader: carve out efi_check_pe() Heinrich Schuchardt
2021-01-14 15:42 ` Simon Glass
2021-01-12 19:58 ` [PATCH 3/3] efi_loader: setting boot device Heinrich Schuchardt
2021-01-19 18:06 ` Simon Glass
2021-01-19 18:43 ` Heinrich Schuchardt
2021-01-20 0:15 ` Simon Glass
2022-04-03 21:08 ` Kyle Evans
2022-04-04 5:09 ` Heinrich Schuchardt
2022-04-04 5:40 ` Kyle Evans
2022-04-04 5:58 ` Heinrich Schuchardt
2022-04-04 14:51 ` Kyle Evans
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-all 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=20210112195842.252946-1-xypron.glpk@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.