From: "Sauro Salomoni" <sauros@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Where to look for CRAMFS
Date: Wed, 3 May 2006 18:15:22 -0300 [thread overview]
Message-ID: <c359a7c00605031415o545d761cha3a3498c9454f3df@mail.gmail.com> (raw)
Greetings.
I have an embedded board using i.MX21.
What I want to know is: how do I tell the kernel where my CRAMFS root
file system is?
I mean, I put it in a specific memory address, but how does the kernel
know where it is?!
What happens here is that the kernel looks in some address and don't
find the Magic Number CRAMFS stores in its own start address. I have a
"bad magic number" msg because my root fs is somewhere else.
Can anyone help me, plz?
Thanks in advance.
Sauro
Engineer
Z Tec
www.ztec.com.br
+55 61 3322-2544
next reply other threads:[~2006-05-03 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 21:15 Sauro Salomoni [this message]
2006-05-04 19:46 ` Where to look for CRAMFS Antonio Di Bacco
-- strict thread matches above, loose matches on Subject: below --
2006-05-04 7:17 Josu Onandia
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=c359a7c00605031415o545d761cha3a3498c9454f3df@mail.gmail.com \
--to=sauros@gmail.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).