From: Wolfgang Denk <wd@denx.de>
To: Lokesh Kumar <kumar.lokesh@wrx-us.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: cramfs mpc8xx 2.4.18
Date: Fri, 13 Feb 2004 20:59:32 +0100 [thread overview]
Message-ID: <20040213195937.13667C1098@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 13 Feb 2004 13:32:34 EST." <294FD9D3403A0340BDAC38E48DCEFFDCA729@RES-EXCH>
In message <294FD9D3403A0340BDAC38E48DCEFFDCA729@RES-EXCH> you wrote:
>
> I have a custom board running 2.4.18 with initrd. Now, I want to make cramfs
> as root filesystem. When I built cramfs support in the kernel and gave it
> root=/dev/mtdblock1 (where my cramfs in correct endian order is stored on
> flash) rootfstype=cramfs, the kernel hangs. MTD support is built in the
> kernel. If I build cramfs as module, then boot my kernel with initrd (ext2)
> and then mount it (on say /mnt), I can read cramfs correctly.
Where does the kernel hang? Which exact boot messages are printed?
Best regards,
Wolfgang Denk
--
See us @ Embedded World, Nuremberg, Feb 17 - 19, Hall 12.0 Booth 440
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Some people march to the beat of a different drummer. And some people
tango!
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-13 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 18:32 cramfs mpc8xx 2.4.18 Lokesh Kumar
2004-02-13 19:59 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-13 19:31 Ruhland, Paul
2004-02-13 19:42 Ruhland, Paul
2004-02-28 0:03 Lokesh Kumar
2004-02-29 16:31 ` Wolfgang Denk
2004-03-01 0:58 Lokesh Kumar
2004-03-05 13:31 Lokesh Kumar
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=20040213195937.13667C1098@atlas.denx.de \
--to=wd@denx.de \
--cc=kumar.lokesh@wrx-us.com \
--cc=linuxppc-embedded@lists.linuxppc.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).