or will
> be inherit some address from a variable? (perhaps this is not obviously
> documented).
>
>
>
>
> On 28 February 2017 at 16:51, Rick Altherr wrote:
>>
>> I've never seen the kernel load address (the start address for copying
>> the kernel imag
+Joel
On Mon, Mar 20, 2017 at 10:52 AM, Maxim Sloyko wrote:
>
>
> On Mon, Mar 20, 2017 at 10:30 AM, Tom Rini wrote:
>>
>> On Mon, Mar 20, 2017 at 10:24:20AM -0700, Maxim Sloyko wrote:
>> > On Sun, Mar 19, 2017 at 9:42 AM, Tom Rini wrote:
>> >
>> > > On Thu, Mar 16, 2017 at 02:36:20PM -0700, Max
I started looking into the Aspeed AST2400/2500 Hash and Crypto Engine
(HACE) because I'm annoyed by the slight delay during FIT hash
calculation. HACE is a single device that does hashing, DES/AES, and
RSA in either immediate mode or via a single command queue.
I looked at drivers/crypto/fsl whic
include/config_distro_bootcmd.h:65 defines BOOTENV_DEV_MMC when
CONFIG_CMD_MMC is defined. Otherwise, line 69 does. In the former case,
BOOTENV_DEV_MMC is defined to BOOTENV_DEV_BLKDEV which is a macro that
takes 3 arguments. In the latter case, BOOTENV_DEV_MMC is defined
to BOOT_TARGET_DEVICES_
How would you verify that the public key hasn't been tampered with?
On Fri, Feb 17, 2017 at 12:37 AM, Maria Sepulveda
wrote:
> Good morning,
>
> I am working with FIT image in U-Boot 2013.07. I have configured the image
> verification with signed image and kernel boots fine so, I would like to
>
> arch = "arm";
> compression = "none";
> fdt-version = <1>;
> hash@1{
> algo = "sha256";
> };
> signature@1{
> algo = "sha256,rsa2048";
> key-name-hint = "dev_key";
> };
> };
>
> Apparently, this causes
.end = 0x2216c0f1
> images.os.load = 0x2200, load_end = 0x22165cc8
> ERROR: new format image overwritten - must RESET the board to recover
> resetting ...
>
> This appears to be an addressing issue. Anyone care to comment?
>
> I'll put up how I got to this point after, but
0x186A00
> #> iminfo
>
> ## Checking Image at 2200 ...
>FIT image found
>FIT description: Configuration to load a Basic Kernel
> Image 0 (linux_kernel@1)
> Description: Linux zImage
> Type: Kernel Image
> Compression: uncompress
Whoops. Thank you for catching that.
Reviewed-by: Rick Altherr
On Mon, Jan 23, 2017 at 7:51 AM, Cédric Schieli wrote:
> In commit c2e7e72, the ramdisk relocation code was moved from
> image_setup_linux to do_bootm, leaving the bootz and booti cases broken.
>
> This patch fixes bo
9 matches
Mail list logo
