On Monday, February 10, 2014 at 07:15:09 AM, Heiko Schocher wrote:
Hello Marek,
Am 08.02.2014 15:09, schrieb Marek Vasut:
On Saturday, January 25, 2014 at 07:44:24 AM, Heiko Schocher wrote:
check if a fdt is correct signed pass an optional addr value. Contains the addr of the key blob
Signed-off-by: Heiko Schocherhs@denx.de Cc: Simon Glasssjg@chromium.org
Should the FIT signature checking really be part of the 'fdt' command ? Shouldn't 'bootm' check the signature (well, 'bootm prep' or such does) or somesuch command ?
Why not? I use this "fdt check" command for example in a script, for checking if the FIT image is correct signed, and if so, update with the binaries in it some UBI Volumes (not only kernel, dt and/or rootfs) ... but if this is not accepted, I can look into the bootm command if I can use it ... but I do not want boot the FIT image ...
But doesn't 'bootm prep' (aka. prepare the image for booting, but do not actually boot) do the same thing ? It does verify the image etc., right ?
Best regards, Marek Vasut