From: David Updegraff <dave@cray.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: mem= flag behaviour
Date: Tue, 11 Jun 2002 11:15:46 -0500 [thread overview]
Message-ID: <3D062232.3010003@cray.com> (raw)
In-Reply-To: 20020611133650.87793.qmail@web15003.mail.bjs.yahoo.com
Hi.
I'm trying to keep a small trace buffer over re-boots
of linux from ppcboot, so give a mem=31M flag to linux
kernel. Yet by the time linux is up, it has overwritten
that memory anyway.. PPCBOOT is properly leaving it
be (with PRAM feature) and correct arg. goes to kernel..
After 'reboot' from linux, the memory contents of
the last meg are still valid (in ppcboot) but by the time linux
is back up, the region has been trashed. Why?
Help, please. How to prevent linux from talking to
that memory region during bootup?
--
David Updegraff / dave@cray.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-11 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 13:36 About IDE_DIRECT on PCMCIA port in ppcboot and linux Dross Zhou
2002-06-11 16:15 ` David Updegraff [this message]
2002-06-11 16:34 ` mem= flag behaviour Wolfgang Denk
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=3D062232.3010003@cray.com \
--to=dave@cray.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).