From mboxrd@z Thu Jan 1 00:00:00 1970 From: Heinrich Schuchardt Date: Tue, 10 Dec 2019 20:32:17 +0100 Subject: [PATCH v2 2/4] bootm: Add a bootm command for type IH_OS_EFI In-Reply-To: References: Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 12/10/19 9:56 AM, Cristian Ciocaltea wrote: > Add support for booting EFI binaries contained in FIT images. > A typical usage scenario is chain-loading GRUB2 in a verified > boot environment. > > Signed-off-by: Cristian Ciocaltea Reading through the code it looks good. What I really need to do is analyze the address usage on the sandbox. To me it is unclear if images->fdt_addr is a physical address or an address in the address space of the sandbox. Did you test this on the sandbox? You can use lib/efi_loader/helloworld.efi as a binary and the 'host load hostfs' command for loading the FIT image. Shouldn't we add booting a UEFI FIT image to the Python test in test/py/tests/test_fit.py? doc/uImage.FIT/signature.txt describes that several properties of the RSA public key should be stored in the control device tree. Unfortunately no example is supplied in which format they should be stored. Could you send me an example, please. I found the following https://github.com/bn121rajesh/ipython-notebooks/blob/master/BehindTheScene/RSAPublicKeyParamsUBoot/rsa_public_key_params_uboot.ipynb Is this an accurate description? Or how do you get the parameters from your RSA public key? Best regards Heinrich