mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: fpg@pengutronix.de, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH v2 0/4] efi: payload: allow extension via fragments
Date: Thu, 15 Oct 2026 11:23:26 +0200	[thread overview]
Message-ID: <20261015092554.210438-1-a.fatoum@pengutronix.de> (raw)

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.

Changes in v2:
  - "efi: payload: ignore ESP state.dtb if device tree is populated":
    check before touching the ESP and only warn if state.dtb actually
    exists, so a built-in state no longer logs a missing file (Fabian)

  - "kbuild: dtc: introduce empty fallback device tree": build
    fallback.dtb on ARM and RISC-V only with CONFIG_EFI_PAYLOAD, so a
    fragment referencing board labels no longer breaks other builds (Anis)

  - "efi: payload: export device tree in barebox-dtb EFI variable": delete
    any existing barebox-dtb variable first, as SetVariable() won't change
    attributes and a non-volatile variable created via efivarfs would
    otherwise survive and be read instead of the exported device tree

  - "Documentation: efi: describe device tree handling": refer to the
    "Load options" section that the series this one applies on adds

  - Rebase onto the load options series instead of next

  - Link to v1: https://lore.barebox.org/barebox/20260826121640.2936023-1-a.fatoum@pengutronix.de/

Ahmad Fatoum (4):
  efi: payload: ignore ESP state.dtb if device tree is populated
  kbuild: dtc: introduce empty fallback device tree
  efi: payload: export device tree in barebox-dtb EFI variable
  Documentation: efi: describe device tree handling

 Documentation/boards/efi.rst | 76 ++++++++++++++++++++++++++++++++++--
 Documentation/user/state.rst |  5 +++
 arch/arm/dts/Makefile        |  4 ++
 arch/riscv/dts/Makefile      |  4 ++
 arch/x86/Kbuild              |  2 +
 arch/x86/dts/Makefile        |  5 +++
 common/fallback.dts          | 10 +++++
 efi/payload/boarddata.c      | 11 ------
 efi/payload/fdt.c            | 56 ++++++++++++++++++++++++++
 efi/payload/handover.c       |  2 +
 efi/payload/image.c          |  2 +
 efi/payload/init.c           | 18 +++++++++
 include/efi/payload.h        |  6 +++
 scripts/Makefile.dtbs        | 10 +++++
 14 files changed, 196 insertions(+), 15 deletions(-)
 create mode 100644 arch/x86/dts/Makefile
 create mode 100644 common/fallback.dts

-- 
2.47.3




             reply	other threads:[~2026-10-15  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  9:23 Ahmad Fatoum [this message]
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 ` [PATCH v2 0/4] efi: payload: allow extension via fragments Sascha Hauer

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=20261015092554.210438-1-a.fatoum@pengutronix.de \
    --to=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