All of lore.kernel.org
 help / color / mirror / Atom feed
From: Diego <diego.ml@zoho.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot multi-file format
Date: Thu, 30 Mar 2017 12:13:16 +0200	[thread overview]
Message-ID: <3013204.RF8YVXT0ez@localhost.localdomain> (raw)
In-Reply-To: <3AEBA8D2-9065-4811-8212-4B2E0F714633@zoho.com>

In data domenica 19 marzo 2017 23:14:14 CEST, Diego ha scritto:
> Hi all,
> 
> I'm trying to use the multi-file format mentioned in pages 12-13 of "U-Boot
> – Multi image booting scenarios" PDF slides.
> 
> I'd like to use FIT format, but I already have units in the field without
> CONFIG_FIT.
> 
> So I'd like to use the legacy U-Boot multi-file format, but I don't
> understand the format that should be used for the ramdisk. I already have a
> multi-file image that boots the kernel with the dtb, but it crashes when
> the ramdisk is needed (looking for an address outside of physical memory
> limits).
> 
> Which format should be used for the ramdisk? ext3.gz initrd? cpio.gz
> initramfs?
> 

Hi all,

as I've found the solution, I'll reply myself in the hope it might help 
somebody in the future.

The format can be both ext3.gz initrd, or cpio.gz, as I've seen a working 
example of ext3.gz initrd here:
https://alteraforum.com/forum/showthread.php?t=51423&p=212064#post212064
And I've been able to make a cpio.gz initramfs by specifying an initrd_high 
address below the location of the multi-file address. Leaving the 
initrd_high=0xffffffff was causing the kernel to not find the ramdisk image, 
thus crashing.

Hope it helps,
Diego

  reply	other threads:[~2017-03-30 10:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-19 22:14 [U-Boot] U-boot multi-file format Diego
2017-03-30 10:13 ` Diego [this message]
2017-03-30 14:19   ` Wolfgang Denk

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=3013204.RF8YVXT0ez@localhost.localdomain \
    --to=diego.ml@zoho.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.