From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@smile.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] boot/uboot: improve U-Boot OP-TEE TEE format options help text
Date: Tue, 10 Mar 2026 23:45:07 +0100 [thread overview]
Message-ID: <e34f413546e5e8bc832dcb74e7793681@free.fr> (raw)
In-Reply-To: <20260304213528.1380898-1-romain.naour@smile.fr>
On 04/03/2026 22:35, Romain Naour via buildroot wrote:
> 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>
Series applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-03-10 22:45 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 ` Julien Olivain via buildroot [this message]
2026-03-20 15:55 ` [Buildroot] [PATCH 1/3] boot/uboot: improve U-Boot OP-TEE TEE format options help text Thomas Perale via buildroot
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=e34f413546e5e8bc832dcb74e7793681@free.fr \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=romain.naour@smile.fr \
/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