From: Steven Vacca <svacca@valcom.com>
To: "LinuxEmbeddedMailList (E-mail)"
<linuxppc-embedded@lists.linuxppc.org>,
"Redhat-devel-list (E-mail)" <redhat-devel-list@redhat.com>
Subject: Local RAM Disk w/mpc8xx-2.2.13
Date: Tue, 23 Oct 2001 09:20:44 -0400 [thread overview]
Message-ID: <01C15BA3.FEB5AAC0.svacca@valcom.com> (raw)
Has anyone ever successfully used Redhat's EDK mpc8xx-2.2.13,
not using NFS for initial RAM Disk access, but using a local initial
RAM Disk (zipped or unzipped) downloaded with the zImage?
I have, in the past, successfully used NFS on the MBX dev bd, and
ran my apps with no problems. Now, on a new custom bd, I am
downloading the init RAM Disk with the zImage, and sometimes it
works and sometimes not. This depends on whether I add or
subtract printk()'s to the kernel code. Modifying the initrd code has
no effect. If I make the RAM Disk zipped or unzipped and make sure
it is copied to a Page-aligned section of RAM, it still exhibits
this same problem. I initially thought the problem was in the gunzipping
of the initrd, but even downloading an unzipped initrd doesn't help.
Help!
Steven
Valcom, Inc.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2001-10-23 13:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=01C15BA3.FEB5AAC0.svacca@valcom.com \
--to=svacca@valcom.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=redhat-devel-list@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.