On 13.03.23 15:42, Ahmad Fatoum wrote: > 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. > > This replaces v2 of the series available in next and fixes the > regressions I introduced for deep-probe systems that ensure probe in > other devices. Ah, not quite, the first patch in v2 is unchanged and I forgot to send it out. @Sascha, let me know if you want me to resend (provided the series is ok now). > > I dropped Jan's Tested-by, because the differences warrant it, but > I tested locally that a RSA key was registered as before. > > v2 was here: > https://lore.barebox.org/barebox/20230210165353.3601175-1-a.fatoum@xxxxxxxxxxxxxx/ > > 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 (3): > boards: qemu-virt: apply overlay at postcore_initcall level > boards: qemu-virt: compile overlay as such > boards: qemu-virt: support passing in FIT public key > > common/boards/qemu-virt/Makefile | 2 +- > common/boards/qemu-virt/board.c | 52 +++++++++++-------- > common/boards/qemu-virt/fitimage-pubkey.dts | 7 +++ > .../{overlay-of-flash.dts => flash.dtso} | 0 > 4 files changed, 38 insertions(+), 23 deletions(-) > create mode 100644 common/boards/qemu-virt/fitimage-pubkey.dts > rename common/boards/qemu-virt/{overlay-of-flash.dts => flash.dtso} (100%) > -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
