From: Dan Malek <dan@netx4.com>
To: "Brown, David (dbrown03)" <DBrown03@harris.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Questions about 8xxrom
Date: Tue, 30 May 2000 13:41:29 -0400 [thread overview]
Message-ID: <3933FD49.3B33F5EF@embeddededge.com> (raw)
In-Reply-To: BE1C564723B3D21191FD0000F840E39801D8154E@rfcmx2.rfc.comm.harris.com
"Brown, David (dbrown03)" wrote:
> ..... But 8xxrom was
> intended to work with disk in addition to flash, so I started exploring why
> ELF-loading didn't work.
There have been lots of changes since I originally wrote the code. I
didn't have the disk loading, but I can speculate on the trouble.
If you are trying to load zImage, it simply isn't going to work. I
am exhausted at explaining why, but one more time.......
The zImage is simple. It is not an ELF image. Strip the 64k header
from the image. Load the bits at or above 0x00200000. Jump to the
first instruction.
If you are loading from a disk, which I presume has a file system, you
know the size of the file. Just load it. I know originally the loader
knew it had to load at or above 0x00200000.......It also knew it was
loading a zImage, and if the ELF header was found knew what it could
believe or not and how to start a zImage. I don't know what the code
looks like today, as I am still using the old stuff from years ago.
> c) The problem with initrd decompression was that the board descriptor data
> was copied explicitly to 0x200000 which happened to be in the middle of
> initrd.
It shouldn't be. You didn't follow the instructions.....Load the zImage
at or above 0x00200000, jump to the first instruction. FYI, 8260 is
load at or above 0x00480000.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-30 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-30 13:35 Questions about 8xxrom Brown, David (dbrown03)
2000-05-30 17:41 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-01 6:49 Duncan Palmer
2000-05-26 13:48 Brown, David (dbrown03)
2000-05-26 16:11 ` Dan Malek
2000-05-29 2:25 ` Graham Stoney
2000-05-29 21:48 ` Dan Malek
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=3933FD49.3B33F5EF@embeddededge.com \
--to=dan@netx4.com \
--cc=DBrown03@harris.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).