From: Ralf Baechle <ralf@uni-koblenz.de>
To: Green <greeen@iii.org.tw>
Cc: LinuxEmbeddedMailList <linux-embedded@waste.org>,
LinuxKernelMailList <linux-kernel@vger.kernel.org>,
MipsMailList <linux-mips@fnet.fr>,
linux-mips@oss.sgi.com
Subject: Re: Discontinuous memory!!
Date: Thu, 1 Nov 2001 02:06:32 +0100 [thread overview]
Message-ID: <20011101020632.A5076@dea.linux-mips.net> (raw)
In-Reply-To: <00c701c1612b$4c133620$4c0c5c8c@trd.iii.org.tw>; from greeen@iii.org.tw on Tue, Oct 30, 2001 at 06:11:43PM +0800
On Tue, Oct 30, 2001 at 06:11:43PM +0800, Green wrote:
> I am porting Linux to R3912.
>
> There are two memory block on my target board.
>
> One is 16MB from 0x8000 0000 to 0x8100 0000.
>
> The other one is 16MB from 0x8200 0000 to 0x8300 0000.
>
> But I found kernel just managed the first memory block.
>
> How could I modify the kernel to support 32MB discontinuous memory?
>
> Now I am trying to add entries to page table.
> It will halt at decompressing ramdisk.
>
> Has anyone resolve this kind of problem before?
The kernel support this type of memory architecture if you enable
CONFIG_DISCONTIGMEM. One machine which uses this feature is the Origin,
grep in arch/mips64 for CONFIG_DISCONTIGMEM. There are also several
ARM system using it.
As support for CONFIG_DISCONTIGMEM is less than perfect you should check
if your system allows for reconfiguration of memory as a single physically
contiguous chunk.
Don't use add_memory_region() in this case; that code only works well
for small holes in memory address space. Your holes are fairly large
so memory management would waste about 2mb if you would not use
CONFIG_DISCONTIGMEM.
Ralf
prev parent reply other threads:[~2001-11-01 1:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00c701c1612b$4c133620$4c0c5c8c@trd.iii.org.tw>
2001-10-30 13:29 ` Discontinuous memory!! Maciej W. Rozycki
2001-11-01 1:06 ` Ralf Baechle [this message]
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=20011101020632.A5076@dea.linux-mips.net \
--to=ralf@uni-koblenz.de \
--cc=greeen@iii.org.tw \
--cc=linux-embedded@waste.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.