linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "David Grab" <d.grab@hima.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: initrd rootfs ramdisk
Date: Tue, 05 Jul 2005 10:18:54 +0200	[thread overview]
Message-ID: <20050705081854.8096B353A4A@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 05 Jul 2005 08:36:46 +0200." <000001c5812b$eb088c70$f201a8c0@SN7606>

In message <000001c5812b$eb088c70$f201a8c0@SN7606> you wrote:
> 
> i solved my problem last problem and now i get console output. :) So next
> step is to setup the root file system. I want to use an image loaded into
> ramdisk, but seems i´m missing something. I´m using u-boot to load the
> ramdisk and linux kernel. Actually i don´t know how the kernel gets the
> location of the loaded ramdisk. I only added the support (see Kernel

It gets passed in registers r4 (start address) and r5 (end address).

> configuration) and the command line parameter root=/dev/ram rw. But the boot
> command arguments from u-boot seems not recognized from the linux kernel.

But the kernel prints the boot parameters just fine.

> Should the option CONFIG_BOOT_LOAD point on the address of the ramdisk? I

No.

> hope someone could help me to trigger out my problem.

Are you sure that you have ext2 filesystem support  enabled  in  your
kernel configuration?

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
I perceive a possibility of an immediate  chronological  sequence  of
events which includes a violence.
                        - Terry Pratchett, _The Dark Side of the Sun_

  reply	other threads:[~2005-07-05  9:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-05  6:36 initrd rootfs ramdisk David Grab
2005-07-05  8:18 ` Wolfgang Denk [this message]
2005-07-05 11:18   ` AW: " David Grab
2005-07-05 16:01     ` Wolfgang Denk
2005-07-06  9:07       ` AW: " David Grab
2005-07-06 10:30         ` David Grab

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=20050705081854.8096B353A4A@atlas.denx.de \
    --to=wd@denx.de \
    --cc=d.grab@hima.com \
    --cc=linuxppc-embedded@ozlabs.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).