mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH v4 0/6] boards: qemu-virt: support passing in FIT public key
Date: Mon, 12 Jun 2023 14:50:58 +0200	[thread overview]
Message-ID: <20230612125104.1082800-1-a.fatoum@pengutronix.de> (raw)

FIT public key is usually passed in via board DT. Usual way to use
barebox with QEMU Virt however is to use DT supplied by Qemu and apply
overlay to it. mkimage doesn't generate overlay DTB though. To make
barbebox Qemu Virt behave like other boards, let's define a dummy DT
that includes CONFIG_BOOTM_FITIMAGE_PUBKEY, which is merged with the
barebox live device tree.

v3 -> v4:
  - early exit initcall if compatible doesn't match
  - evaluate DTC_CPP_FLAGS for device tree overlays
  - rename overlay to reference board name
  - Rename older QEMU's /soc/flash@X to /flash@X

v2 -> v3:
  - drop "support of_ensure_probed for top-level machine device"
  - switch from board driver back to initcall

v1 -> v2:
  - support of_ensure_probed for top-level machine device
  - ensure qemu board driver is probed at postcore

Ahmad Fatoum (6):
  boards: qemu-virt: apply overlay at postcore_initcall level
  kbuild: support DTC_CPP_FLAGS_file.dtbo
  boards: qemu-virt: compile overlay as such
  boards: qemu-virt: support passing in FIT public key
  of: implement of_move_node helper
  boards: qemu-virt: support older QEMU with /soc/flash

 common/boards/qemu-virt/Makefile              |  6 +-
 common/boards/qemu-virt/board.c               | 62 ++++++++++++-------
 common/boards/qemu-virt/fitimage-pubkey.dts   |  7 +++
 ...rlay-of-flash.dts => qemu-virt-flash.dtso} |  0
 drivers/of/base.c                             | 18 ++++++
 include/of.h                                  |  1 +
 scripts/Makefile.lib                          |  1 +
 7 files changed, 69 insertions(+), 26 deletions(-)
 create mode 100644 common/boards/qemu-virt/fitimage-pubkey.dts
 rename common/boards/qemu-virt/{overlay-of-flash.dts => qemu-virt-flash.dtso} (100%)

-- 
2.39.2




             reply	other threads:[~2023-06-12 12:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 12:50 Ahmad Fatoum [this message]
2023-06-12 12:50 ` [PATCH v4 1/6] boards: qemu-virt: apply overlay at postcore_initcall level Ahmad Fatoum
2023-06-12 12:51 ` [PATCH v4 2/6] kbuild: support DTC_CPP_FLAGS_file.dtbo Ahmad Fatoum
2023-06-12 12:51 ` [PATCH v4 3/6] boards: qemu-virt: compile overlay as such Ahmad Fatoum
2023-06-12 12:51 ` [PATCH v4 4/6] boards: qemu-virt: support passing in FIT public key Ahmad Fatoum
2023-06-12 12:51 ` [PATCH v4 5/6] of: implement of_move_node helper Ahmad Fatoum
2023-06-13  8:27   ` Sascha Hauer
2023-06-13  8:30     ` Ahmad Fatoum
2023-06-13  8:32       ` Sascha Hauer
2023-06-12 12:51 ` [PATCH v4 6/6] boards: qemu-virt: support older QEMU with /soc/flash Ahmad Fatoum

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=20230612125104.1082800-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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