From: David Daney <ddaney@avtrex.com>
To: James Zipperer <jamesz@modsystems.com>
Cc: linux-mips@linux-mips.org
Subject: Re: smp8634 add memory at dram1
Date: Mon, 03 Mar 2008 16:26:55 -0800 [thread overview]
Message-ID: <47CC974F.3090306@avtrex.com> (raw)
In-Reply-To: <2D30722FBBDE6749973243F4F01BE984A242CA@dotexchange.dotcorporation.com>
James Zipperer wrote:
>
>
>
> I'm running out of memory in linux on the smp86xx and attempting to
> implement this solution. Did you ever get it to work? No luck for me
> yet. I'm still a bit unclear why you must switch linux to run off DRAM
> 1 instead of leaving it on DRAM 0 and adding an additional call to
> add_memory_region in prom_init for DRAM 1. But then again, I haven't
> gotten that to work yet either :)
>
>
>
> Any info/patches are greatly appreciated. Thanks!
>
>
>
Typically DRAM 1 must be accessed through the TLB as its address lays
outside of the 512MB window of KSEG[012].
The best way to make this memory available to Linux may still be up for
debate.
David Daney
next prev parent reply other threads:[~2008-03-04 0:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 0:14 smp8634 add memory at dram1 James Zipperer
2008-03-04 0:14 ` James Zipperer
2008-03-04 0:26 ` David Daney [this message]
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
[not found] <5DF100B598199744B111FCEA5222E78A01CB9F5F@sigma-exch1.sdesigns.com>
2007-12-04 2:22 ` David Kuk
[not found] <5DF100B598199744B111FCEA5222E78A02D52DCE@sigma-exch1.sdesigns.com>
2007-11-22 7:35 ` David Kuk
-- strict thread matches above, loose matches on Subject: below --
2007-11-14 8:44 David Kuk
2007-11-14 11:04 ` 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
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=47CC974F.3090306@avtrex.com \
--to=ddaney@avtrex.com \
--cc=jamesz@modsystems.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