diff options
author | mario.six@gdsys.cc <mario.six@gdsys.cc> | 2016-07-20 08:32:50 +0200 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2016-07-25 12:00:05 -0400 |
commit | e8fb4358c2ea3b5629f004f7d0d5624c860d7e70 (patch) | |
tree | 13b128109c4db4d4a1a56bb828f0c634a9f06ad6 /common/main.c | |
parent | bcdc1c8376c55fcc8b8fdd7f27f117eff0bf715d (diff) | |
download | u-boot-imx-e8fb4358c2ea3b5629f004f7d0d5624c860d7e70.zip u-boot-imx-e8fb4358c2ea3b5629f004f7d0d5624c860d7e70.tar.gz u-boot-imx-e8fb4358c2ea3b5629f004f7d0d5624c860d7e70.tar.bz2 |
common: fit: Allow U-Boot images to be booted
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@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@1 {
algo = "sha256,rsa4096";
key-name-hint = "key";
};
};
};
Signed-off-by: Mario Six <mario.six@gdsys.cc>
Reviewed-by: Tom Rini <trini@konsulko.com>
Diffstat (limited to 'common/main.c')
0 files changed, 0 insertions, 0 deletions