From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/5] efi_loader: run a specific efi application more easily
Date: Tue, 15 Jan 2019 11:54:32 +0900 [thread overview]
Message-ID: <20190115025437.11966-1-takahiro.akashi@linaro.org> (raw)
This patch is a result from re-organizing my previous patches;
a combination of [1] and part of [2] so as to solely provide several ways
of executing a specific efi application explicitly.
* bootmanager via BootNext variable
* bootefi with boot id
* run -e with BootXXXX variable
Changes in v2 (Jan 15, 2019)
* not specify any attributes when deleting BootNext variable in
efi_bootmgr_load()
* introduce EFI_BOOTMGR_DEFAULT_ORDER macro on behalf of BootOrder
for use in efi_bootmgr_load()
* simplify the code around efi_handle_fdt() in do_bootefi()
* add do_bootefi_run() and call it at "run -e" so that we don't have to
export internal efi helper functions
[1] https://lists.denx.de/pipermail/u-boot/2018-November/349281.html
[2] https://lists.denx.de/pipermail/u-boot/2018-November/346450.html
AKASHI Takahiro (5):
efi_loader: bootmgr: support BootNext and BootCurrent variable
behavior
efi_loader: bootmgr: allow for running a given load option
cmd: bootefi: carve out fdt parameter handling
cmd: bootefi: run an EFI application of a specific load option
cmd: run: add "-e" option to run an EFI application
cmd/bootefi.c | 114 +++++++++++++++++++++++++++--------
cmd/nvedit.c | 9 ++-
common/cli.c | 10 +++
include/command.h | 3 +
include/efi_loader.h | 5 +-
lib/efi_loader/efi_bootmgr.c | 43 ++++++++++++-
6 files changed, 156 insertions(+), 28 deletions(-)
--
2.19.1
next reply other threads:[~2019-01-15 2:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 2:54 AKASHI Takahiro [this message]
2019-01-15 2:54 ` [U-Boot] [PATCH v2 1/5] efi_loader: bootmgr: support BootNext and BootCurrent variable behavior AKASHI Takahiro
2019-02-26 18:57 ` Heinrich Schuchardt
2019-02-27 5:47 ` AKASHI Takahiro
2019-02-27 6:14 ` Heinrich Schuchardt
2019-02-27 6:27 ` AKASHI Takahiro
2019-02-27 6:39 ` Heinrich Schuchardt
2019-02-27 6:55 ` AKASHI Takahiro
2019-01-15 2:54 ` [U-Boot] [PATCH v2 2/5] efi_loader: bootmgr: allow for running a given load option AKASHI Takahiro
2019-01-15 2:54 ` [U-Boot] [PATCH v2 3/5] cmd: bootefi: carve out fdt parameter handling AKASHI Takahiro
2019-01-15 2:54 ` [U-Boot] [PATCH v2 4/5] cmd: bootefi: run an EFI application of a specific load option AKASHI Takahiro
2019-02-26 19:30 ` Heinrich Schuchardt
2019-02-27 5:58 ` AKASHI Takahiro
2019-02-27 6:31 ` Heinrich Schuchardt
2019-02-27 6:47 ` AKASHI Takahiro
2019-02-27 19:33 ` Heinrich Schuchardt
2019-02-28 4:28 ` AKASHI Takahiro
2019-02-28 4:47 ` Heinrich Schuchardt
2019-01-15 2:54 ` [U-Boot] [PATCH v2 5/5] cmd: run: add "-e" option to run an EFI application AKASHI Takahiro
2019-02-26 19:20 ` Heinrich Schuchardt
2019-02-27 6:12 ` AKASHI Takahiro
2019-02-27 6:25 ` Heinrich Schuchardt
2019-02-27 6:37 ` AKASHI Takahiro
2019-02-27 7:10 ` Heinrich Schuchardt
2019-02-28 4:45 ` AKASHI Takahiro
2019-02-28 4:53 ` Heinrich Schuchardt
2019-02-28 5:06 ` AKASHI Takahiro
2019-02-28 5:13 ` Heinrich Schuchardt
2019-03-01 1:22 ` AKASHI Takahiro
2019-03-05 2:48 ` AKASHI Takahiro
2019-02-28 20:59 ` Heinrich Schuchardt
2019-03-01 1:26 ` AKASHI Takahiro
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=20190115025437.11966-1-takahiro.akashi@linaro.org \
--to=takahiro.akashi@linaro.org \
--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.