From: Florian Fainelli <florian.fainelli@telecomint.eu>
To: supinlick@yahoo.com
Cc: linux-mips@linux-mips.org
Subject: Re: Linux Boot RAM Determination
Date: Tue, 17 Jun 2008 20:15:43 +0200 [thread overview]
Message-ID: <200806172015.48426.florian.fainelli@telecomint.eu> (raw)
In-Reply-To: <368058.32705.qm@web51908.mail.re2.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
Hello Sean,
Le Tuesday 17 June 2008 19:45:01 Sean Parker, vous avez écrit :
> Hello -
>
> We're developing a PMC-Sierra RM9000 system, and when Linux boots it
> seems to only see 256M RAM (cat /proc/meminfo -> MemTotal=256M), despite a
> Crucial 1GB double-sided SODIMM card.
>
> The boot code is PMON, and it recognizes all 1GB (dimm0:2 Ranks each
> 512MB) and prints as much when it's done.
>
> Is there a setting in the Linux source (we're using a single elf image
> with ramfs integrated) that might be limiting the MemTotal/RAM size found
> by Linux? I couldn't find anywhere in the Linux code (patched by PMC) that
> mentions reading the DDR DCR's to inspect what the configured RAM
> sizes/offsets are. Any ideas?
Did you check the code which reserves memory for ther kernel ? Most boards
will set this in either prom or setup code :
pmc-sierra/msp71xx/msp_prom.c: add_memory_region(base, size, type);
pmc-sierra/yosemite/setup.c: add_memory_region(0x00000000, 0x10000000,
BOOT_MEM_RAM);
If your code is based on yosemite, it seems like it should get the memsize
parameter from the bootloader, instead of hardcoding it to 256Mb like it
currently does.
Hope it helps you.
--
Cordialement, Florian Fainelli
------------------------------
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-06-17 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 17:45 Linux Boot RAM Determination Sean Parker
2008-06-17 18:15 ` Florian Fainelli [this message]
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=200806172015.48426.florian.fainelli@telecomint.eu \
--to=florian.fainelli@telecomint.eu \
--cc=linux-mips@linux-mips.org \
--cc=supinlick@yahoo.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