From: "Subbu Linux" <subbu.linux@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Linux with e500 v2 core, can we support Ram base address starting at 0x1_0000_0000
Date: Tue, 15 Jan 2008 15:16:59 -0500 [thread overview]
Message-ID: <f807f08a0801151216l59400ca0i746424a84befc7a8@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
Hi
I am currently working on MPC8548 core, would like to know wheather current
Linux with e500v2 core supporting Physical Address of RAM at 0x1_0000_0000,
I know in current linux with large Page table support we can access devices
at 0x1_0000_0000 for e500v2, but I wanted to move RAM base address to
0x1_0000_0000, so that I can support larger RAM. Can any body suggest me if
their is any patch available for this or is it possible to implement from
scratch.
Thanks
Subbu
[-- Attachment #2: Type: text/html, Size: 551 bytes --]
next reply other threads:[~2008-01-15 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 20:16 Subbu Linux [this message]
2008-01-18 15:52 ` Linux with e500 v2 core, can we support Ram base address starting at 0x1_0000_0000 Kumar Gala
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=f807f08a0801151216l59400ca0i746424a84befc7a8@mail.gmail.com \
--to=subbu.linux@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).