linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: "Anoop P.A." <Anoop_P.A@pmc-sierra.com>
Cc: linux-mips@linux-mips.org
Subject: Re: 1 GB RAM with RM9000 SOC
Date: Mon, 25 Jan 2010 09:15:21 -0800	[thread overview]
Message-ID: <4B5DD1A9.6020306@caviumnetworks.com> (raw)
In-Reply-To: <A7DEA48C84FD0B48AAAE33F328C020140474B674@BBY1EXM11.pmc_nt.nt.pmc-sierra.bc.ca>

Anoop P.A. wrote:
> Hi list,
> 
>  
> 
> Any of you successfully used >512MB ram with MIPS SOC's.

Does Cavium Octeon count as a MIPS SOC?  If so, then yes.

I have many boards with both 2GB and 4GB.  All of them Linux just fine 
when using all available RAM.

> I have a
> requirement where I have to use 1 GB ram with RM9000 based SOC. 
> 
> I have enabled 64 Bit support and so far it is working with 512 MB of
> RAM. How ever if I increase memory beyond 512MB I am getting kernel
> panic.
> 
>  
> 
>  I am adding memory region from 0x00 add_memory_region(0 ,0x40000000 ,
> BOOT_MEM_RAM). (PMON maps RAM from 0x0 to 0x40000000)  Am I wrong here?
> 
>  
> 
> It will be great if you can give some suggestion /point me to a working
> implementation. I am using 2.6.18 kernel.
> 
>  
> 
> Thanks
> 
> Anoop
> 
> 
> 
> 

  parent reply	other threads:[~2010-01-25 17:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19 23:59 [PATCH] MIPS: cleanup switches with cases that can be merged Roel Kluin
2010-01-20  2:02 ` David Daney
2010-01-20 11:47   ` Alexander Clouter
2010-01-23 16:31   ` Ralf Baechle
2010-01-24  0:23 ` Ralf Baechle
2010-01-24 17:58   ` 1 GB RAM with RM9000 SOC Anoop P.A.
2010-01-24 17:58     ` Anoop P.A.
2010-01-25 17:15     ` David Daney [this message]
2010-01-25 17:34       ` Anoop P.A.
2010-01-25 17:34         ` Anoop P.A.
2010-01-25 17:38         ` 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=4B5DD1A9.6020306@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=Anoop_P.A@pmc-sierra.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;
as well as URLs for NNTP newsgroup(s).