linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Pokki <kalle.pokki@iki.fi>
To: dhlii@comcast.net
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Need help Understanding initial memory conditions.
Date: Tue, 18 Oct 2005 23:14:24 +0300	[thread overview]
Message-ID: <435557A0.8090505@iki.fi> (raw)
In-Reply-To: <435549C2.1000106@dlasys.net>

David H. Lynch Jr. wrote:

> Kalle Pokki wrote:
>
>> 1. Put RAM to 0x0000000 and flash to some location it mirrors to your 
>> boot vector. Linux always expects your physical memory to be at zero. 
>> It is then mapped to virtual address 0xC0000000.
>
>    In both this list and elsewhere I have seen several references to 
> the difficulty setting up Linux with a physical RAM base other than 
> 0x0. I was hoping that I could bypass that by re-arranging physical 
> memory using the BAT's or MMU.
> I am gathering that while this is possible, that it not sufficient. 
> That if memory is re-arranged after power-on it has to be done by 
> something Linux is not aware of.

I'm afraid you cannot fool Linux that way... it will take control of the 
BATs and MMU. Even as a concept, you cannot re-arrange physical memory 
with the MMU at all - it's virtual memory when you do the address 
translation. The only way to arrange physical memory is to program the 
memory controller. I don't know how flexible the OCM controller in 
ppc405 is, but I'd be surprised if one couldn't freely set the addresses 
to whatever suits best.

  reply	other threads:[~2005-10-18 20:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18  8:04 Need help Understanding initial memory conditions David H. Lynch Jr
2005-10-18  8:49 ` Kalle Pokki
2005-10-18 19:15   ` David H. Lynch Jr.
2005-10-18 20:14     ` Kalle Pokki [this message]
2005-10-19  5:16       ` David H. Lynch Jr
2005-10-19  6:37         ` Kalle Pokki
2005-10-19 10:24           ` Andrei Konovalov

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=435557A0.8090505@iki.fi \
    --to=kalle.pokki@iki.fi \
    --cc=dhlii@comcast.net \
    --cc=linuxppc-embedded@ozlabs.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).