From: David Jander <david.jander@protonic.nl>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Memory map with "holes"...
Date: Tue, 12 Aug 2003 14:32:09 +0200 [thread overview]
Message-ID: <200308121432.09782.david.jander@protonic.nl> (raw)
Hi all,
We are designing a board based on the MPC852T (MPC866 serivate), and
I want to make sure there is the possibility to mount different-size
SDRAM chips on it, so I just connect the two bank-select pins to some
higher address lines, leaving some out in between, in order to acomodate
for bigger chips in the future. The bottom line is that I will get the
memory map split up into 4 segments with vast holes between each segment
that are undefined. What do I need to keep in mind regarding linux
about this? I suppose it isn't an issue, but I want to be sure I don't
get any trouble later. Any experience with memory holes? I suppose the
boot-loader should tell the kernel about the memory-map, in a way just
like lilo on an x86 machine, am I right? Does this work the same way on
linux-ppc ?
Greetings,
--
David Jander
Protonic Holland.
tel.: +31 (0) 229 212928
fax.: +31 (0) 229 210930
Factorij 36 / 1628 AL Zwaag
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-08-12 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 12:32 David Jander [this message]
2003-08-12 14:13 ` Memory map with "holes" Wolfgang Denk
2003-08-12 15:00 ` David Jander
2003-08-12 15:41 ` Wolfgang Denk
[not found] ` <3F391DA1.4040202@esteem.com>
2003-08-13 8:36 ` Memory map with "holes"... (slightly off-topic) David Jander
2002-02-15 7:31 ` Shall I use which IRQ as input parameter of this function? John Zhou
2003-08-13 17:01 ` Memory map with "holes"... (slightly off-topic) Conn Clark
-- strict thread matches above, loose matches on Subject: below --
2003-08-12 19:36 Memory map with "holes" Conn Clark
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=200308121432.09782.david.jander@protonic.nl \
--to=david.jander@protonic.nl \
--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).