From: Tom Rini <trini@konsulko.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>, u-boot@lists.denx.de
Subject: Re: [PATCH v4 1/1] efi_loader: expose the device-tree file name
Date: Tue, 24 Oct 2023 14:03:46 -0400 [thread overview]
Message-ID: <20231024180346.GD496310@bill-the-cat> (raw)
In-Reply-To: <20231024062032.8543-1-heinrich.schuchardt@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
On Tue, Oct 24, 2023 at 08:20:32AM +0200, Heinrich Schuchardt wrote:
> Forward and backward compatibility of Linux kernel device-trees is
> sometimes missing. One solution approach is to load a kernel specific
> device-tree. This can either be done via a U-Boot scripts (like the one
> generated by Debian package flash-kernel or by a boot loader like GRUB.
> The boot loader approach currently requires to know the device-tree name
> before first boot which makes it unusable for generic images.
>
> Expose the device-tree file name as EFI variable FdtFile.
> This will allow bootloaders to load a kernel specific device-tree.
>
> The variable will not be exposed on ACPI based systems or if the
> environment variable fdtfile is not defined.
>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-10-24 18:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 6:20 [PATCH v4 1/1] efi_loader: expose the device-tree file name Heinrich Schuchardt
2023-10-24 18:02 ` Simon Glass
2023-10-25 18:23 ` Simon Glass
2023-10-25 19:57 ` Heinrich Schuchardt
2023-10-25 20:12 ` Tom Rini
2023-10-25 20:28 ` Mark Kettenis
2023-10-25 20:51 ` Heinrich Schuchardt
2023-10-25 21:05 ` Simon Glass
2023-10-25 21:13 ` Tom Rini
2023-10-25 21:22 ` Heinrich Schuchardt
2023-11-03 19:44 ` Simon Glass
2025-03-23 18:38 ` Caleb Connolly
2025-03-28 12:01 ` Simon Glass
2025-03-28 13:00 ` Caleb Connolly
2025-03-28 14:18 ` Heinrich Schuchardt
2025-03-30 14:38 ` Caleb Connolly
2025-03-31 16:30 ` Tom Rini
2025-03-31 16:39 ` Heinrich Schuchardt
2025-04-01 15:48 ` Simon Glass
2023-10-24 18:03 ` Tom Rini [this message]
2023-10-24 19:28 ` Ilias Apalodimas
2023-10-24 19:33 ` Ilias Apalodimas
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=20231024180346.GD496310@bill-the-cat \
--to=trini@konsulko.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=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 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.