Hi, Any help on this question ? Am I missing something basic ? why signer(mkimage) needs to produce the fitImage and uboot dtb as single step.

---------- Forwarded message ---------- From: shr ch shrads.june@gmail.com Date: Thu, Apr 28, 2016 at 4:34 PM Subject: mkimage needs fitImage To: u-boot@lists.denx.de

Hi,

For adding public keys to uboot dtb the mkimage step is

mkimage -D "-I dts -O dtb -p 2000" -F -k keys -K u-boot.dtb -r fitImage

It resigns fitImage and adds public key to uboot dtb

but why do we need fitImage for adding public keys to uboot dtb ? can't this be two different steps ? there is already a step to just build fitImage.

This creates unnecessary dependency of building fitImage before building uboot.