From: Tom Rini <trini@konsulko.com>
To: Jamin Lin <jamin_lin@aspeedtech.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] uboot-sign: support to load optee-os and TFA images
Date: Wed, 17 Jan 2024 22:24:57 -0500 [thread overview]
Message-ID: <20240118032457.GZ12635@bill-the-cat> (raw)
In-Reply-To: <SI2PR06MB5041B4FBF62741BAB50A66CDFC712@SI2PR06MB5041.apcprd06.prod.outlook.com>
On Thu, Jan 18, 2024 at 02:19:09AM +0000, Jamin Lin wrote:
> > -----Original Message-----
> > From: Tom Rini <trini@konsulko.com>
> > Sent: Wednesday, January 17, 2024 10:37 PM
> > To: Jamin Lin <jamin_lin@aspeedtech.com>
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: Re: [PATCH] uboot-sign: support to load optee-os and TFA images
> >
> > On Tue, Jan 16, 2024 at 07:37:04PM -0800, Jamin Lin wrote:
> >
> > > Hi Alexander,
> > >
> > > One more thing, So far, bitman only support hash 256.
> >
> > What hashing algorithm would you like to be using instead? We can always
> > include more and better options with configuration as needed.
> >
> > --
> > Tom
>
> Hi Tom
> At present, makeimage tool support hash 256, 384 and 512. It also support rsa 2038, 3072 and 4096.
> It would be better if binman support these algorithms.
>
> I patched uboot-sign.bbclass the original goal is to make yocto support optee-os and tfa in the old version of u-boot.
Right, but it would be best if OE leveraged binman I believe and in turn
you made binman support taking the hash algorithm as an input as needed.
--
Tom
next prev parent reply other threads:[~2024-01-18 3:25 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 [this message]
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=20240118032457.GZ12635@bill-the-cat \
--to=trini@konsulko.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