public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Jamin Lin" <jamin_lin@aspeedtech.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] uboot-sign: support to load optee-os and TFA images
Date: Tue, 16 Jan 2024 17:54:28 -0800	[thread overview]
Message-ID: <17005.1705456468183527781@lists.openembedded.org> (raw)
In-Reply-To: <8f804eb9fff6b055a4d53198fa4553242e1204af.camel@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 803 bytes --]

Hi Alexander,

Thanks for review.

I tested it in ASPEED AST2600 and AST2700 SOCs. Yoc can see our Github repository here.

https://github.com/AspeedTech-BMC

You are right the latest version of u-boot(2024.01) support binman python tool to create FIT image and support optee-os and trusted-firmware-a.

However, “the old version of u-boot binman python tool” did not support to add optee-os and trusted-firmware-a in the FIT image.

For example, our AST2600 is production and its u-boot version was 2019.04 and binman python tools did not support optee-os image format.

That was why I changed ITS file creation scripts to support all u-boot version.

Finally, users are able to use the “makeimage” tool to crate FIT image with optee-os and trusted-firmware-a.

Thanks-Jamin

[-- Attachment #2: Type: text/html, Size: 1955 bytes --]

  reply	other threads:[~2024-01-17  1: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 ` [OE-core] " Sverdlin, Alexander
2024-01-17  1:54   ` Jamin Lin [this message]
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=17005.1705456468183527781@lists.openembedded.org \
    --to=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