Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Kuk <david.kuk@entone.com>
To: linux-mips@linux-mips.org
Subject: smp8634 add memory at dram1
Date: Wed, 14 Nov 2007 16:44:27 +0800	[thread overview]
Message-ID: <473AB56B.2070107@entone.com> (raw)

After study about the memory configuration of sigma smp8634, i found 
some difficult to accomplish the task.

so my question is if have two 128MB ram separately under dram0 and dram1 
controller, where dram0 for linux and dram1 for video decoding. Now the 
situation is the memory for linux is not enough and video decoding can 
not use all of it's 128MB at dram1, what we plan to do is to share 64MB 
at dram1 to the linux kernel as high memory, and only reserved 64MB at 
dram1 for the video decoding.

first, in MIPS architecture, we found that the kseg0 and kseg1 are 
mapped to 0x00000000-0x20000000, which include only dram0 controller, so 
we wish to add the dram1 memory manually to the kernel using function 
add_memory_region at setup.c , after booting up result the warning that 
the memory larger than 512 need to configured the kernel support high 
memory.

then when we configure the kernel to support high memory at menu 
configure, the kernel when booting up will remind us our CPU do not 
support high memory due to cache aliases.

Both way will lead the linux can not boot up normally, so what should we 
do, is there any mis-understanding about the hardware implementation or 
MIPS design? \

             reply	other threads:[~2007-11-14  8:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14  8:44 David Kuk [this message]
2007-11-14 11:04 ` smp8634 add memory at dram1 Ralf Baechle
2007-11-14 12:36   ` david
2007-11-14 16:09 ` David Daney
2007-11-15 10:49   ` Gustafsson Marcus-MGU001
2007-11-15 10:49     ` Gustafsson Marcus-MGU001
2007-11-20  4:22   ` David Kuk
     [not found] <5DF100B598199744B111FCEA5222E78A02D52DCE@sigma-exch1.sdesigns.com>
2007-11-22  7:35 ` David Kuk
     [not found] <5DF100B598199744B111FCEA5222E78A01CB9F5F@sigma-exch1.sdesigns.com>
2007-12-04  2:22 ` David Kuk
  -- strict thread matches above, loose matches on Subject: below --
2008-03-04  0:14 James Zipperer
2008-03-04  0:14 ` James Zipperer
2008-03-04  0:26 ` David Daney
2008-03-04  1:59   ` James Zipperer
2008-03-04  1:59     ` James Zipperer
2008-03-04 20:51     ` James Zipperer
2008-03-04 20:51       ` James Zipperer

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=473AB56B.2070107@entone.com \
    --to=david.kuk@entone.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