Re: [isar-cip-core][PATCH 6/8] add kas files for building qemu secure boot images

[Jan Kiszka <jan.kiszka@siemens.com>]

On 24.10.22 14:27, sven.schultschik@siemens.com wrote:
> From: Sven Schultschik <sven.schultschik@siemens.com>
> 
> The u-boot-efi-ebg-op-tee-qemu kas file combines the different recipes to create an image which can be booted with qemu and provides secure boot with EBG, TFA, u-boot, UEFI, EDK2, OPTEE and RPMB
> 
> Signed-off-by: Sven Schultschik <sven.schultschik@siemens.com>
> ---
>  kas/opt/u-boot-efi-ebg-op-tee-qemu.yml | 11 +++++++++++
>  1 file changed, 11 insertions(+)
>  create mode 100644 kas/opt/u-boot-efi-ebg-op-tee-qemu.yml
> 
> diff --git a/kas/opt/u-boot-efi-ebg-op-tee-qemu.yml b/kas/opt/u-boot-efi-ebg-op-tee-qemu.yml
> new file mode 100644
> index 000000000..0558c8e79
> --- /dev/null
> +++ b/kas/opt/u-boot-efi-ebg-op-tee-qemu.yml
> @@ -0,0 +1,11 @@
> +header:
> +  version: 10
> +  includes:
> +    - kas/board/qemu-arm64.yml
> +    - kas/opt/5.10.yml
> +    - kas/opt/bullseye.yml
> +    - kas/opt/ebg-secure-boot-snakeoil.yml
> +
> +local_conf_header:  
> +  trusted-firmware-a-qemu-arm64: |
> +    IMAGE_INSTALL_append = " trusted-firmware-a-qemu-arm64"
> \ No newline at end of file

Why is this still needed? As discussed, we want to have (QEMU) u-boot
with TFA and OPTEE when secure boot is selected.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux