From: Ralf Baechle <ralf@linux-mips.org>
To: "Figo.zhang" <figo1802@gmail.com>
Cc: Kevin Hickey <khickey@netlogicmicro.com>, linux-mips@linux-mips.org
Subject: Re: how to support more than 512MB RAM for MIPS32 ?
Date: Wed, 25 Nov 2009 16:00:47 +0000 [thread overview]
Message-ID: <20091125160047.GA10490@linux-mips.org> (raw)
In-Reply-To: <1259163074.2049.6.camel@myhost>
On Wed, Nov 25, 2009 at 11:31:14PM +0800, Figo.zhang wrote:
> how to do map extra RAM to any ouside I/O space?
> it is just motify:
>
> 1. arch/mips/kernel/setup.c: bootm_init()function, motity the define
> "HIGHMEM_START", for me:
> #define HIGHMEM_START 0x2000,0000 //512MB
Leave HIGHMEM_START unchanged; it should always be 512MB no matter what
the actual memory addresses of a particular platform are. The kernel
needs to treat anything above 512MB differently because it's not
permanently mapped and HIGHMEM_START stands for this limit.
Ralf
next prev parent reply other threads:[~2009-11-25 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 6:34 how to support more than 512MB RAM for MIPS32 ? figo zhang
2009-11-25 14:37 ` Kevin Hickey
2009-11-25 15:31 ` Figo.zhang
2009-11-25 16:00 ` Ralf Baechle [this message]
2009-11-25 16:17 ` Figo.zhang
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=20091125160047.GA10490@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=figo1802@gmail.com \
--cc=khickey@netlogicmicro.com \
--cc=linux-mips@linux-mips.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