From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] common: fit: Allow U-Boot images to be booted
Date: Wed, 20 Jul 2016 08:27:37 -0400 [thread overview]
Message-ID: <20160720122737.GV7260@bill-the-cat> (raw)
In-Reply-To: <20160720063250.19532-1-mario.six@gdsys.cc>
On Wed, Jul 20, 2016 at 08:32:50AM +0200, Mario Six wrote:
> In certain circumstances it comes in handy to be able to boot into a second
> U-Boot. But as of now it is not possible to boot a U-Boot binary that is inside
> a FIT image, which is problematic for projects that e.g. need to guarantee a
> unbroken chain of trust from SOC all the way into the OS, since the FIT signing
> mechanism cannot be used.
>
> This patch adds the capability to load such FIT images.
>
> An example .its snippet (utilizing signature verification) might look
> like the following:
>
> images {
> firmware at 1 {
> description = "2nd stage U-Boot image";
> data = /incbin/("u-boot-dtb.img.gz");
> type = "firmware";
> arch = "arm";
> os = "u-boot";
> compression = "gzip";
> load = <0x8FFFC0>;
> entry = <0x900000>;
> signature at 1 {
> algo = "sha256,rsa4096";
> key-name-hint = "key";
> };
> };
> };
>
> Signed-off-by: Mario Six <mario.six@gdsys.cc>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160720/b74b3384/attachment.sig>
next prev parent reply other threads:[~2016-07-20 12:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 6:32 [U-Boot] [PATCH v2] common: fit: Allow U-Boot images to be booted Mario Six
2016-07-20 12:27 ` Tom Rini [this message]
2016-07-20 12:59 ` Robert P. J. Day
2016-07-20 13:39 ` Mario Six
2016-07-20 13:56 ` Robert P. J. Day
2016-07-20 14:26 ` Mario Six
2016-07-21 10:56 ` Robert P. J. Day
2016-07-26 2:32 ` [U-Boot] [U-Boot, " Tom Rini
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=20160720122737.GV7260@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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