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
