Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: <linux-mips@reliableembeddedsystems.com>
To: linux-mips@linux-mips.org
Cc: linux-mips@reliabeembeddedsystems.com
Subject: SMP8634 DRAM memory issue
Date: Sat, 20 Sep 2008 00:09:08 -0500	[thread overview]
Message-ID: <4e9ae533d87732773b7ad0f1a33b54f9@reliableembeddedsystems.com> (raw)

Hi,

We've got an SMP8634 based set-top box from a 3rd party and are trying to
port some middleware to it.
Everything seems to work out fine, except for one thing ... the amount of
memory for kernel space.

The box physically has two 64MB chips and two 32MB chips.  
The kernel is only seeing the two 32MB chips, apparently attached to DRAM0.

The problem is the following:

1) The middleware requires more memory in kernel space to allocalte big
graphical surfaces.
2) Whatever runs before the kernel is also from a 3rd party and we don't
have access to it.
3) We can't change anything on the box hardware.

This means, we would only be able to patch starting from the Linux kernel.

Do you see any way to swap what the kernel sees to be 128MB instead of 64MB
and the user space 64MB minus whatever is allocated for the initial RAM
disc?
The 64MB for user space are sufficient, we just need more then 64 MB on
kernel space.

Regards,

Robert

-- 
Robert Berger
Embedded Software Specialist

Reliable Embedded Systems
Consulting Training Engineering
Tel.: (+30) 697 593 3428
Fax.:(+30 210) 684 7881
URL: http://www.reliableembeddedsystems.com
--
...This above all: to thine own self be true.-- Shakespeare

             reply	other threads:[~2008-09-20  5:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-20  5:09 linux-mips [this message]
2008-09-20  7:07 ` SMP8634 DRAM memory issue David Daney

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=4e9ae533d87732773b7ad0f1a33b54f9@reliableembeddedsystems.com \
    --to=linux-mips@reliableembeddedsystems.com \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-mips@reliabeembeddedsystems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox