From: "Figo.zhang" <figo1802@gmail.com>
To: Kevin Hickey <khickey@netlogicmicro.com>
Cc: ralf@linux-mips.org, linux-mips@linux-mips.org
Subject: Re: how to support more than 512MB RAM for MIPS32 ?
Date: Wed, 25 Nov 2009 23:31:14 +0800 [thread overview]
Message-ID: <1259163074.2049.6.camel@myhost> (raw)
In-Reply-To: <1259159857.4675.11.camel@kh-d280-64>
On Wed, 2009-11-25 at 08:37 -0600, Kevin Hickey wrote:
> We use HIGHMEM on the Au1300 to access any memory spaces >256 MB. Our
> I/O area starts at 256 MB. We just map the extra DRAM to any area
> outside the I/O space,
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
2. use add_memory_region, for me:
add_memory_region(0x20000000, 0x40000000, BOOT_MEM_RAM); //extra 1G RAM
is it ok ?
Best,
Figo.zhang
> enable highmem, and register it as BOOT_MEM_RAM
> with add_memory_region. Works great.
>
> =Kevin
> --
> Kevin Hickey
> Netlogic Microsystems
>
>
> On Wed, 2009-11-25 at 14:34 +0800, figo zhang wrote:
> > hi all,
> >
> > I am using 24KEC SOC, i want to support larger more than 512MB RAM.
> > The mips32 architure in Kseg0/Kseg1,
> > such as:
> > 0x8000,0000 ~ 0x92c0,0000 # 300MB for RAM
> > 0x92c0,0000 ~ 0xa000,0000 # 212 for I/O register
> >
> > so, mips32 only support 300MB memory, i dont how to support more than
> > 512MB in linux-mips kernel , such as 2GB memory? it is using HIGHMEM
> > strategy
> > for kernel(ZONE_HIGHMEM)?
> >
> > Best,
> > Figo.zhang
>
next prev parent reply other threads:[~2009-11-25 15:29 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 [this message]
2009-11-25 16:00 ` Ralf Baechle
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=1259163074.2049.6.camel@myhost \
--to=figo1802@gmail.com \
--cc=khickey@netlogicmicro.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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