public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Shawn Jin <shawnxjin@gmail•com>
To: John Otken <jotken@softadvances•com>,
	ppcembed <linuxppc-embedded@ozlabs•org>
Subject: Re: 2.6.10 unable to mount a root fs on ramdisk
Date: Wed, 25 May 2005 10:48:45 -0700	[thread overview]
Message-ID: <c3d0340b05052510483145039e@mail.gmail.com> (raw)
In-Reply-To: <4292A441.4080708@softadvances.com>

Hi John,

Thanks for your answer.

I did add these lines to the code. Actually it turned out that I was
so stupid that I didn't enable EXT2 filesystem support in the kernel.
That's why the kernel always complained unknown block.

-Shawn.

On 5/23/05, John Otken <jotken@softadvances•com> wrote:
> I had this problem with MV code on a Bamboo board.  Look at
> platform_init() in ebony.c.  Before the call to ibm44x_platform_init() ad=
d:
>=20
>        /*
>         * If we were passed in a board information, copy it into the
>         * residual data area.
>         */
>        if (r3)
>                __res =3D *(bd_t *)(r3 + KERNELBASE);
>=20
>        /*
>         * If the init RAM disk has been configured in, and there's a vali=
d
>         * starting address for it, set it up.
>         */
>        if (r4) {
>            initrd_start =3D r4 + KERNELBASE;
>            initrd_end =3D r5 + KERNELBASE;
>        }
>=20
>        /* Copy the kernel command line arguments to a safe place. */
>=20
>        if (r6) {
>            *(char *) (r7 + KERNELBASE) =3D 0;
>            strcpy(cmd_line, (char *) (r6 + KERNELBASE));
>        }

      parent reply	other threads:[~2005-05-25 17:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 22:17 2.6.10 unable to mount a root fs on ramdisk Shawn Jin
     [not found] ` <4292A441.4080708@softadvances.com>
2005-05-25 17:48   ` Shawn Jin [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=c3d0340b05052510483145039e@mail.gmail.com \
    --to=shawnxjin@gmail$(echo .)com \
    --cc=jotken@softadvances$(echo .)com \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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