public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@smile.fr>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] boot/uboot: improve U-Boot OP-TEE TEE format options help text
Date: Fri, 20 Mar 2026 16:55:07 +0100	[thread overview]
Message-ID: <20260320155507.176738-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260304213528.1380898-1-romain.naour@smile.fr>

In reply of:
> OP-TEE generates a few binaries that can be used by u-boot on some
> platforms (Rockchip, Texas Instruments K3) using TEE variable.
> 
> Add a link to the OP-TEE documentation were we can find easily the
> desciption for each TEE format that can be used by u-boot.
> 
> For convenience, copy tee.elf and tee.bin description in each option
> choice help text.
> 
> Signed-off-by: Romain Naour <romain.naour@smile.fr>

Applied to 2025.02.x & 2026.02.x. Thanks

> ---
>  boot/uboot/Config.in | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/boot/uboot/Config.in b/boot/uboot/Config.in
> index 47ce24ee76..17b7f95f50 100644
> --- a/boot/uboot/Config.in
> +++ b/boot/uboot/Config.in
> @@ -295,15 +295,23 @@ choice
>  	  Since this version, the TEE in binary format must be used as
>  	  it contains important meta-data.
>  
> +	  https://optee.readthedocs.io/en/4.9.0/architecture/porting_guidelines.html#binaries
> +
>  config BR2_TARGET_UBOOT_NEEDS_OPTEE_TEE_ELF
>  	bool "tee.elf"
>  	help
> +	  The main OP-TEE ELF file. All other OP-TEE binaries are
> +	  created with this as input.
> +
>  	  ELF format may be used only for OP-TEE versions before
>  	  3.8.0.
>  
>  config BR2_TARGET_UBOOT_NEEDS_OPTEE_TEE_BIN
>  	bool "tee.bin"
>  	help
> +	  The original OP-TEE binary with a header (v1) and combined
> +	  init, paged, and unpaged parts.
> +
>  	  Binary format must be used for OP-TEE versions since 3.8.0.
>  
>  endchoice
> -- 
> 2.52.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-03-20 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 21:35 [Buildroot] [PATCH 1/3] boot/uboot: improve U-Boot OP-TEE TEE format options help text Romain Naour via buildroot
2026-03-04 21:35 ` [Buildroot] [PATCH 2/3] boot/uboot: add support for embedded TEE in raw binary format Romain Naour via buildroot
2026-03-04 21:35 ` [Buildroot] [PATCH 3/3] configs/beagleboneai64_defconfig: use BR2_TARGET_UBOOT_NEEDS_OPTEE_TEE_RAW_BIN Romain Naour via buildroot
2026-03-10 22:45 ` [Buildroot] [PATCH 1/3] boot/uboot: improve U-Boot OP-TEE TEE format options help text Julien Olivain via buildroot
2026-03-20 15:55 ` Thomas Perale via buildroot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260320155507.176738-1-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=romain.naour@smile.fr \
    --cc=thomas.perale@mind.be \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox