On 26/02/18 15:26, Andrew F. Davis wrote:
Lets look at u-boot/include/image.h for a moment, the table of IH_TYPE_* already has a type for what we are trying to do here: IH_TYPE_KERNEL. The comment on this table describes "OS Kernel Images" as exactly what you are doing with your TEE image.
To me what you really want to do is add a new IH_OS_*, which are defined in a different table above (I see this is already done for ATF (IH_OS_ARM_TRUSTED_FIRMWARE) which shares a similar “boot-through” flow like Philipp pointed out).
So I'm still not sure what the technical reason you need a new "type" of image, when adding your hooks to the existing IH_TYPE_KERNEL path in U-Boot could be made to do the same thing when it encounters a IH_OS_TEE
I'll have a look and see if your suggestion on IH_TYPE_KERNEL is feasible, it looks like is though I don't know for sure until I try.
i.e. "mkimage -A arm -T kernel -C none -d tee.bin uTee.optee" + hook on the OPTEE header on the IH_TYPE_KERNEL path.
--- bod