linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Fundu <fundu_1999@yahoo.com>
Cc: linux-embedded <linux-embedded@vger.kernel.org>
Subject: Re: initrd and uImage
Date: Mon, 11 Aug 2008 22:56:41 +0200	[thread overview]
Message-ID: <20080811205641.GB9467@game.jcrosoft.org> (raw)
In-Reply-To: <54582.81328.qm@web63407.mail.re1.yahoo.com>

On 09:42 Fri 08 Aug     , Fundu wrote:
> Hi,
> First off i have a ppc based board.
> and i'm trying to load a kernel image with ramdisk rootfs.

Which version of U-Boot do you use?
Which features do you enable?

> 
> i have build the kernel. it spit uImage,zImage and vmlinux.gz
> 
> my question are.
> 1) what are all the different image types ? 
> i know the uImage is just the kernel, what are the rest (zImage & vmlinux.gz)?
> 
> 2) i'm using u-boot as the bootldr. so i download the uImage (cause zImage and vmlinux.gz aren't bootlable) from tftp server and then do bootm <address> the kernel only load partially. How does the kernel know where/how to load the rootfs ? 

It's depend on which uImage you use.

In U-Boot, you can generate a Multi-File Image with the ramdisk inside,
FDT, multiple configuration etc...

In the case you describe you are supposed to download the ramdisk via
tftp also and set the kernel parameter via the bootargs variable and do
bootm.

example

U-Boot> tftp 200000 uImage
U-Boot> tftp a00000 uRamdisk
U-Boot> bootm 200000 a00000

good examples on these pages

http://www.denx.de/wiki/view/DULG/Manual
http://www.denx.de/wiki/view/DULG/RootFileSystemOnARamdisk
http://www.denx.de/wiki/view/DULG/CombiningKernelAndRamdisk

Best Regards,
J.

      parent reply	other threads:[~2008-08-11 20:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08 16:42 initrd and uImage Fundu
2008-08-08 18:16 ` Robert Schwebel
2008-08-11 16:12 ` Tim Bird
2008-08-11 17:17   ` Josh Boyer
2008-08-11 20:56 ` Jean-Christophe PLAGNIOL-VILLARD [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=20080811205641.GB9467@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --cc=fundu_1999@yahoo.com \
    --cc=linux-embedded@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).