From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"jamin_lin@aspeedtech.com" <jamin_lin@aspeedtech.com>
Subject: Re: [OE-core] [PATCH] uboot-sign: support to load optee-os and TFA images
Date: Tue, 16 Jan 2024 07:54:19 +0000 [thread overview]
Message-ID: <8f804eb9fff6b055a4d53198fa4553242e1204af.camel@siemens.com> (raw)
In-Reply-To: <20240115075416.393025-1-jamin_lin@aspeedtech.com>
Hello Jamin!
On Mon, 2024-01-15 at 15:54 +0800, Jamin Lin via lists.openembedded.org wrote:
> Currently, u-boot FIT image only support to load u-boot image.
> To support optee-os and trusted-firmware-a, update ITS file generation
> scripts, so users are able to use u-boot FIT image to load
> u-boot, optee-os and treustred-firmware-a images
>
> Add a variable "UBOOT_FIT_ARM_TRUSTED_FIRMWARE_A" to
> enable trusted-firmware-a image and it is disable by default.
>
> Add a variable "UBOOT_FIT_OPTEE_OS" to enable optee-os image
> and it is disable by default.
Have you considered leveraging the existing binman infrastructure in the recent
U-Boot for TF-A and OPTEE?
Which platform are you testing on?
There is TI K3 documentation already [1], but many parts of the new infrastructure
are not TI specific as I understand...
> The ITS file creation loos like as following.
[]
[1] Link: https://source.denx.de/u-boot/u-boot/-/blob/master/doc/board/ti/k3.rst?ref_type=heads&plain=1
--
Alexander Sverdlin
Siemens AG
www.siemens.com
next prev parent reply other threads:[~2024-01-16 7:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 7:54 [PATCH] uboot-sign: support to load optee-os and TFA images Jamin Lin
2024-01-16 7:54 ` Sverdlin, Alexander [this message]
2024-01-17 1:54 ` Jamin Lin
2024-01-17 3:37 ` Jamin Lin
2024-01-17 14:37 ` Tom Rini
2024-01-18 2:19 ` Jamin Lin
2024-01-18 3:24 ` Tom Rini
2024-02-14 11:57 ` [OE-core] " Sverdlin, Alexander
2024-02-15 1:56 ` Jamin Lin
2024-01-16 12:18 ` Jörg Sommer
2024-01-17 1:55 ` Jamin Lin
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=8f804eb9fff6b055a4d53198fa4553242e1204af.camel@siemens.com \
--to=alexander.sverdlin@siemens.com \
--cc=jamin_lin@aspeedtech.com \
--cc=openembedded-core@lists.openembedded.org \
/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