From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: fpg@pengutronix.de
Subject: Re: [PATCH v2 0/4] efi: payload: allow extension via fragments
Date: Thu, 15 Oct 2026 15:07:09 +0200 [thread overview]
Message-ID: <179206962993.2298281.16159482816371778683.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20261015092554.210438-1-a.fatoum@pengutronix.de>
On Thu, 15 Oct 2026 11:23:26 +0200, Ahmad Fatoum wrote:
> CONFIG_EXTERNAL_DTS_FRAGMENTS can't be used with the EFI payload, because
> it has no internal DT at build-time and until recently not even a DT at
> runtime.
>
> This series adds the necessary bits to have this work the same on
> non-EFI-payload platforms.
>
> [...]
Applied, thanks!
[1/4] efi: payload: ignore ESP state.dtb if device tree is populated
https://git.pengutronix.de/cgit/barebox/commit/?id=df4e979e8b8e (link may not be stable)
[2/4] kbuild: dtc: introduce empty fallback device tree
https://git.pengutronix.de/cgit/barebox/commit/?id=756c8a432495 (link may not be stable)
[3/4] efi: payload: export device tree in barebox-dtb EFI variable
https://git.pengutronix.de/cgit/barebox/commit/?id=21a84d913166 (link may not be stable)
[4/4] Documentation: efi: describe device tree handling
https://git.pengutronix.de/cgit/barebox/commit/?id=9dd077fdf33a (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-10-15 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 9:23 Ahmad Fatoum
2026-10-15 9:23 ` [PATCH v2 1/4] efi: payload: ignore ESP state.dtb if device tree is populated Ahmad Fatoum
2026-10-15 9:23 ` [PATCH v2 2/4] kbuild: dtc: introduce empty fallback device tree Ahmad Fatoum
2026-10-15 9:23 ` [PATCH v2 3/4] efi: payload: export device tree in barebox-dtb EFI variable Ahmad Fatoum
2026-10-15 9:23 ` [PATCH v2 4/4] Documentation: efi: describe device tree handling Ahmad Fatoum
2026-10-15 13:07 ` Sascha Hauer [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=179206962993.2298281.16159482816371778683.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=fpg@pengutronix.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