All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 26 May 2000 12:11:19 -0400	[thread overview]
Message-ID: <392EA227.41945656@embeddededge.com> (raw)
In-Reply-To: BE1C564723B3D21191FD0000F840E39801D81549@rfcmx2.rfc.comm.harris.com


"Brown, David (dbrown03)" wrote:

>
> Now, I've gone back to try the ELF method.  My flash starts at FF800000, and
> the zImage.initrd is stored at the beginning of flash.


As I have said many times, and as recently as yesterday, the zImage
(especially with initrd) was never intended to be a proper ELF image.
It is the most compressed set of bits possible to minimize storage
in a device.  The ELF header is an artifact of the tools used to create
zImage, and should simply be stripped.  The zImage is a "self extracting"
image that is loaded into ram or flash rom.  When you are loading this
from a file system or via TFTP, you know the size to load into memory.
If you are loading from some medium, like a raw flash card, you have
to make some assumptions about the size or tack a few bytes on the front
that indicate the length.  Most systems have some custom boot loader
that requires a special, very small header, or they just jump to the
start of the image in flash rom.


	-- Dan

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

  reply	other threads:[~2000-05-26 16:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-26 13:48 Questions about 8xxrom Brown, David (dbrown03)
2000-05-26 16:11 ` Dan Malek [this message]
2000-05-29  2:25 ` Graham Stoney
2000-05-29 21:48   ` Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
2000-05-30 13:35 Brown, David (dbrown03)
2000-05-30 17:41 ` Dan Malek
2000-06-01  6:49 Duncan Palmer

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=392EA227.41945656@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.