public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
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: Wed, 14 Feb 2024 11:57:43 +0000	[thread overview]
Message-ID: <dff1bbe651fa6733fb6034c9505aa200e7377df8.camel@siemens.com> (raw)
In-Reply-To: <8f804eb9fff6b055a4d53198fa4553242e1204af.camel@siemens.com>

Hello Jamin,

On Tue, 2024-01-16 at 08:54 +0100, Alexander Sverdlin wrote:
> 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?

BTW, there has been a recent FOSDEM talk on
"Standardizing the generation and signing of boot images":

https://fosdem.org/2024/schedule/event/fosdem-2024-3067-standardizing-the-generation-and-signing-of-boot-images/

> 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

  parent reply	other threads:[~2024-02-14 11:57 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 ` [OE-core] " Sverdlin, Alexander
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   ` Sverdlin, Alexander [this message]
2024-02-15  1:56     ` [OE-core] " 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=dff1bbe651fa6733fb6034c9505aa200e7377df8.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