* Re: Discontinuous memory!!
[not found] <00c701c1612b$4c133620$4c0c5c8c@trd.iii.org.tw>
@ 2001-11-01 1:06 ` Ralf Baechle
0 siblings, 0 replies; only message in thread
From: Ralf Baechle @ 2001-11-01 1:06 UTC (permalink / raw)
To: Green; +Cc: LinuxEmbeddedMailList, LinuxKernelMailList, MipsMailList,
linux-mips
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2001-11-01 1:10 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <00c701c1612b$4c133620$4c0c5c8c@trd.iii.org.tw>
2001-11-01 1:06 ` Discontinuous memory!! Ralf Baechle
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox