linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: John Whitney <john.whitney@timesys.com>
To: Prakash Kanthi <pkanthi@yahoo.com>,
	"Mailing List: linuxppc-embedded"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Max RAM for Linux only 1GB?
Date: Fri, 31 Oct 2003 12:28:55 -0500	[thread overview]
Message-ID: <BBC80607.2081%john.whitney@timesys.com> (raw)
In-Reply-To: <20031031165821.17006.qmail@web41215.mail.yahoo.com>


Prakash,

The easiest route it to turn on highmem support (CONFIG_HIGHMEM).  As far as
I know, this does work for the PowerPC.  My understanding is that the kernel
doesn't directly use this memory, but will allow user-space programs to use
it (mapped into their memory space), which should in turn free up the memory
the kernel DOES use.

I think you'll need to start playing with the kernel start address if you
want the kernel to benefit directly from the additional memory.  I know this
has been done successfully to 0xA0000000, not sure about all the way down to
0x80000000 (but I can't think of why it wouldn't off the top of my head).

John

On 10/31/03 11:58 AM, "Prakash Kanthi" <pkanthi@yahoo.com> wrote:

>
> Folks,
>
> I have over 1GB DIMM RAM on my board running PPC 405.
> How can i ioremap that to my OS? As Linux virtual
> space starts at 0xC0000000, we have only 1GB more for
> all virtual space mappings.
>
> Even if i move 0xC0000000 to 0x80000000, what will
> happen to TLB settings? Any problem there to map 1GB
> additional RAM?
>
> Any idea as to how i can do this?
>
> Thanks,
> Prakash
>
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-10-31 17:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-31 16:58 Max RAM for Linux only 1GB? Prakash Kanthi
2003-10-31 17:28 ` John Whitney [this message]
2003-10-31 18:25 ` Matt Porter

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=BBC80607.2081%john.whitney@timesys.com \
    --to=john.whitney@timesys.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=pkanthi@yahoo.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 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).