From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: u-boot@lists.denx.de
Subject: [PATCH 0/8 v2] Change logic of EFI LoadFile2 protocol for initrd loading
Date: Wed, 30 Dec 2020 23:17:44 +0200 [thread overview]
Message-ID: <X+zueLqxm9qvXHD4@enceladus> (raw)
In-Reply-To: <2a0b4a86-0c36-f46f-1ce9-3f73693eca51@gmx.de>
Hi Heinrich,
On Wed, Dec 30, 2020 at 09:44:39PM +0100, Heinrich Schuchardt wrote:
> On 12/30/20 4:07 PM, Ilias Apalodimas wrote:
> > Hi!
> >
> > This is v2 of [1].
> >
> > There's been a couple of changes regarding where we install the protocol.
> > The initial patchset was completely disregarding BootNext, so that's taken
> > into account now and we can use the new feature.
> > This brought a few changes on the selftests as well, since we now use the
> > loaded image handle to install the protocol, as a consequence the custom
> > handle in the tests is now uninstalled during the test .teardown(), but
> > the overall approach remains identical.
>
> Boot#### contains a device path.
>
> Why should Initrd#### contain something U-Boot specific and not a device
> path?
Because there was no standard on it, since we used the path as a config option
up to now I just kept it as is.
>
> Think of a Linux distribution. When updating the kernel it will have to
> write Boot#### and Initrd####. It can determine the current boot device
> via BootCurrent and Boot####. Next it can add the new file paths for
> Boot#### and Initrd#### relative to the same device.
This isn't a bad idea. Let me update the patch and send a v3.
Cheers
/Ilias
prev parent reply other threads:[~2020-12-30 21:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 15:07 [PATCH 0/8 v2] Change logic of EFI LoadFile2 protocol for initrd loading Ilias Apalodimas
2020-12-30 15:07 ` [PATCH 1/8 v2] efi_loader: Remove unused headers from efi_load_initrd.c Ilias Apalodimas
2020-12-30 18:21 ` Heinrich Schuchardt
2020-12-30 15:07 ` [PATCH 2/8 v2] efi_loader: Remove unconditional installation of file2 protocol for initrd Ilias Apalodimas
2020-12-30 18:15 ` Heinrich Schuchardt
2020-12-30 15:07 ` [PATCH 3/8 v2] efi_loader: Add size checks to efi_create_indexed_name() Ilias Apalodimas
2020-12-30 18:34 ` Heinrich Schuchardt
2020-12-30 21:23 ` Ilias Apalodimas
2020-12-30 15:07 ` [PATCH 4/8 v2] efi_loader: Introduce helper functions for EFI Ilias Apalodimas
2020-12-30 19:29 ` Heinrich Schuchardt
2020-12-30 21:21 ` Ilias Apalodimas
2020-12-30 15:07 ` [PATCH 5/8 v2] efi_loader: bootmgr: Use get_var from efi_helper file Ilias Apalodimas
2020-12-30 19:32 ` Heinrich Schuchardt
2020-12-30 15:07 ` [PATCH 6/8 v2] efi_loader: Replace config option with EFI variable for initrd loading Ilias Apalodimas
2020-12-30 19:38 ` Heinrich Schuchardt
2021-01-05 2:42 ` AKASHI Takahiro
2021-01-05 8:50 ` Ilias Apalodimas
2021-01-06 10:43 ` Ilias Apalodimas
2021-01-06 11:07 ` Heinrich Schuchardt
2021-01-06 12:53 ` Ilias Apalodimas
2020-12-30 15:07 ` [PATCH 7/8 v2] efi_selftest: Modify self-tests for initrd loading via Loadfile2 Ilias Apalodimas
2020-12-30 20:29 ` Heinrich Schuchardt
2020-12-30 15:07 ` [PATCH 8/8 v2] doc: uefi: Add instruction for initrd loading Ilias Apalodimas
2020-12-30 20:17 ` Heinrich Schuchardt
2020-12-30 20:44 ` [PATCH 0/8 v2] Change logic of EFI LoadFile2 protocol " Heinrich Schuchardt
2020-12-30 21:17 ` Ilias Apalodimas [this message]
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=X+zueLqxm9qvXHD4@enceladus \
--to=ilias.apalodimas@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox