From: Wolfgang Denk <wd@denx.de>
To: T Ziomek <ctz001@email.mot.com>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: AW: AW: AW: initrd rootfs ramdisk
Date: Fri, 22 Jul 2005 01:33:02 +0200 [thread overview]
Message-ID: <20050721233302.BDBF5352B83@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 21 Jul 2005 16:12:18 CDT." <Pine.WNT.4.61.0507211609080.2672@holyoke.labs.mot.com>
In message <Pine.WNT.4.61.0507211609080.2672@holyoke.labs.mot.com> you wrote:
>
> Sigh...found it, after weeks of on-and-off work... Our board has 64 MB of
> RAM but I'm passing "mem=32M" to the kernel because we want our app to man-
> age the high 32 MB.
>
> U-Boot defaults to copying an initrd into the highest available RAM. That
> put it in an area outside of Linux's knowledge, D'OH. All I had to do was
> set U-Boot's 'initrd_high' env var and things work.
Note: if you want the content of this reserved area to survice
warmboots you can enable the "protected RAM" feature in U-Boot
(CONFIG_PRAM), and it will not touch this area at all. Useful for
things like pramfs for example :-)
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
Never worry about theory as long as the machinery does what it's
supposed to do. - R. A. Heinlein
prev parent reply other threads:[~2005-07-21 23:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050720203355.027CF67CF6@ozlabs.org>
2005-07-20 22:05 ` AW: AW: initrd rootfs ramdisk T Ziomek
2005-07-21 7:30 ` AW: " David Grab
2005-07-21 21:12 ` T Ziomek
2005-07-21 23:33 ` Wolfgang Denk [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=20050721233302.BDBF5352B83@atlas.denx.de \
--to=wd@denx.de \
--cc=ctz001@email.mot.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).