All of lore.kernel.org
 help / color / mirror / Atom feed
From: ypresente@mrv.com (Yaron Presente)
To: linux-mips@linux-mips.org
Subject: non-contiguous physical memory
Date: Thu, 24 Jun 2004 15:46:43 +0300	[thread overview]
Message-ID: <40DACD33.60801@mrv.com> (raw)

Hi all,
I'm running montavista linux (2.4.18_mvl30-malta-mips_fp_le) on a board 
that has 2 memory banks of physical memory.
1. 32MB from physical address 0x00000000
2. 16MB from physical address 0x20000000

Currently I can only access the first bank (by add_memory_region(0, 32 
<< 20, BOOT_MEM_RAM) in prom_init() ).
I tried the obvious solution of adding another region at 0x20000000 
(add_memory_region(0x20000000, 16 << 20, BOOT_MEM_RAM))
but that didn't seem to work. I've also tried to add a BOOT_MEM_RESERVED 
region in between the regions in order to create a seemingly contiguous 
memory, with no success.
My questions are:
Is it possible to access the second bank as well under MIPS ?
Is there a way to define a "hole" in the physical memory?
Do I have to use CONFIG_DISCONTIGMEM ? is it fully supported ?
Thanks for your help,

-- 
Yaron Presente
MRV International
Direct   : 972-4-9936237
Fax      : 972-4-9890564
Email   : ypresente@mrv.com
www.mrv.com

             reply	other threads:[~2004-06-24 12:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24 12:46 Yaron Presente [this message]
2004-06-24 23:31 ` non-contiguous physical memory Ralf Baechle
2004-06-27  8:06   ` Yaron Presente
  -- strict thread matches above, loose matches on Subject: below --
2009-01-21 15:18 Non-contiguous " Aaron Pace
2009-01-21 17:28 ` Kumar Gala
2009-01-21 18:00   ` Aaron Pace
2009-01-21 23:25     ` Kumar Gala
2009-01-23 17:52   ` Michele Pallaro
2009-01-23 19:50     ` Kumar Gala

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=40DACD33.60801@mrv.com \
    --to=ypresente@mrv.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 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.