linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Need help Understanding initial memory conditions.
Date: Tue, 18 Oct 2005 15:15:14 -0400	[thread overview]
Message-ID: <435549C2.1000106@dlasys.net> (raw)
In-Reply-To: <4354B707.6060002@iki.fi>

Kalle Pokki wrote:

> David H. Lynch Jr wrote:
>
>>    What exactly is the minimal startup system state the Linux 2.6.13 
>> Kernel expects ?
>
>
> It's pretty hard to describe the system state fully, as there are so 
> many registers it may depend on. However, I can point out a few things 
> from your setup:
>
> 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.

>
> 2. You don't need to have MMU enabled.

    There is a god. I am a compitent developer with lots of low level 
experience, but I have thus far completely missed out on both PPC 
assembler and memory management.

>
> 3. Make sure your boot arguments are passed properly to the kernel. 
> This includes the settings in registers r3 ... r7 and the bd_info 
> structure . There are many variants of that structure, make sure you 
> use the same ones in the boot loader and in Linux.

    That I should have no problem with.


>
>

Thank You very much

  reply	other threads:[~2005-10-18 19:36 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. [this message]
2005-10-18 20:14     ` Kalle Pokki
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=435549C2.1000106@dlasys.net \
    --to=dhlii@dlasys.net \
    --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).