From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michal Simek <michal.simek@xilinx.com>
Date: Tue, 19 Jul 2016 07:46:16 +0200
Subject: [U-Boot] [PATCH] common: fit: Allow U-Boot images to be booted
In-Reply-To: <20160718120542.18598-1-mario.six@gdsys.cc>
References: <20160718120542.18598-1-mario.six@gdsys.cc>
Message-ID: <578DBEA8.30700@xilinx.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 18.7.2016 14:05, 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 {
> 	kernel at 1 {
> 		description = "2nd stage U-Boot image";
> 		data = /incbin/("u-boot-dtb.img.gz");
> 		type = "kernel";

Isn't this type weird for u-boot itself?

The rest is good.

Thanks,
Michal