Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] u-boot .img rootfs
Date: Tue, 6 Mar 2012 17:59:40 +0100	[thread overview]
Message-ID: <20120306175940.19e6f808@skate> (raw)
In-Reply-To: <ADE657CA350FB648AAC2C43247A983F001F41FF55761@AUSP01VMBX24.collaborationhost.net>

Le Tue, 6 Mar 2012 10:48:10 -0600,
H Hartley Sweeten <hartleys@visionengravers.com> a ?crit :

> The only things I have found about the U-Boot image file mentions
> using 'mkimage' to create the file using a command like these
> examples:
> 
> mkimage -T ramdisk -C gzip -n 'Test Ramdisk Image' -d ramdisk.img.gz
> uRamdisk mkimage -A sh -O linux -T ramdisk -a 0x8C800000 -n "ST40
> Linux ramdisk" -d initrd.img /export/ramdisk.ub
> 
> My guess the uRamdisk file is the same format as the uImage file used
> for the kernel. But, I'm not sure what the format of the
> ramdisk.img.gz or initrd.img files are.

Yes, you have to pass the ext2.gz file through mkimage before giving it
to U-Boot, in order to generate a ramdisk image that U-Boot can
understand and load into memory.

However, this way of doing ramdisks is more or less deprecated,
initramfs have been the norm since quite some years now.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2012-03-06 16:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06  2:00 [Buildroot] u-boot .img rootfs H Hartley Sweeten
2012-03-06 10:48 ` Thomas Petazzoni
2012-03-06 16:48   ` H Hartley Sweeten
2012-03-06 16:59     ` Thomas Petazzoni [this message]

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=20120306175940.19e6f808@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox