linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: diekema_jon <diekema@bucks.si.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: EST SBC8260 Linux memory mapping rules
Date: Fri, 19 May 2000 21:34:24 -0400	[thread overview]
Message-ID: <3925EBA0.ABFE1267@embeddededge.com> (raw)
In-Reply-To: m12sxXK-001SyZC@bucks


diekema_jon wrote:

>         - The compressed Linux kernel (zImage) contains a bootstrap loader
>           that is position independent; you can load it into any RAM,
>           ROM or FLASH memory address >= 0x00200000 (above 2 MB).
>
>           Note: If zImage is loaded at its link address of 0x00400000 (4 MB),
>                 then zImage will skip the step of moving itself to
>                 its link address.

The zImage should be loaded above the link address by at least the
amount of memory required by the uncompress/setup functions.  If you
load it below the address, it could potentially relocate itself on
top of the kernel or ram disk image.  For example, the uncompress/setup
functions are linked to run at 0x00400000, based upon the current size
of the functions, you need to load above 0x00407000.  I would pick
0x00480000 or higher, just to not worry about it.


>           and I/O devices above phsical address 0x80000000.  The lowest

You could fix this typo....it should be 'physical'.



	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-05-20  1:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-20  0:54 EST SBC8260 Linux memory mapping rules diekema_jon
2000-05-20  1:34 ` Dan Malek [this message]
2000-05-20  2:49   ` diekema_jon
2000-05-20  4:47     ` Dan Malek
2000-05-22 16:43       ` Wait Queue bug triggered on EST SBC8260 diekema_jon
2000-05-24 20:14         ` diekema_jon
2000-05-24 20:24           ` Joe Green
2000-05-24 20:29           ` Joe Green

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=3925EBA0.ABFE1267@embeddededge.com \
    --to=dan@netx4.com \
    --cc=diekema@bucks.si.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).