From: Dan Malek <dan@mvista•com>
To: Matt Porter <mporter@mvista•com>
Cc: "tsombakos, mark" <tsombakos_mark@emc•com>,
"'linuxppc-embedded@lists•linuxppc.org'"
<linuxppc-embedded@lists•linuxppc.org>
Subject: Re: Booting Sandpoint 8240??
Date: Thu, 22 Feb 2001 15:30:52 -0500 [thread overview]
Message-ID: <3A9576FC.6F4B1FAB@mvista.com> (raw)
In-Reply-To: 20010222083031.A21599@cx258813-a.chnd1.az.home.com
Matt Porter wrote:
> You don't need to do a thing, all is well. :)
Ummmm....I think this should work, but those addresses weren't my
original intention. The original "design" was to use 0x00800000
as the link address, and 0x00900000 as the load address. The code
will copy itself down to the 8 Meg location, then uncompress as you
describe. I don't know if this is still the case, but the uncompress
code used to make some assumptions (take some liberties) about using
the space between the load address and execute address for temporary
storage. If you load below the execute address, this address
arithmetic is screwed up and I'm not sure what would happen.
With the 2.4 kernel you have to allow almost 1.5 Mbytes of space
from the start of RAM for the kernel to do its work, and not write
over some boot information (command line or initrd info) that the
initial bootloader may have dropped into magical memory locations.
Trying to run a bootloader under the 2M boundary is risky, and it
won't run in under the 1.5 M boundary.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-22 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 18:26 Booting Sandpoint 8240?? tsombakos, mark
2001-02-22 15:30 ` Matt Porter
2001-02-22 20:30 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-20 19:36 tsombakos, mark
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=3A9576FC.6F4B1FAB@mvista.com \
--to=dan@mvista$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=mporter@mvista$(echo .)com \
--cc=tsombakos_mark@emc$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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