From: Peter Bergner <bergner@brule.borg.umn.edu>
To: Tom Rini <trini@kernel.crashing.org>
Cc: hollis@austin.ibm.com,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@lists.linuxppc.org,
Debian PowerPC <debian-powerpc@lists.debian.org>,
dan@debian.org
Subject: Re: yaboot & zImage's
Date: Fri, 21 Sep 2001 14:40:50 -0500 [thread overview]
Message-ID: <20010921144050.A223060@brule.borg.umn.edu> (raw)
In-Reply-To: <20010921113329.C23691@cpe-24-221-152-185.az.sprintbbd.net>
Sorry, I should have been a little more explicit. Yes, I meant to
say zImage (including zImage.initrd, duh). No, yaboot does not
do compression.
The only reason we couldn't boot zImages before, was that yaboot
_always_ loaded the image from the FS into memory at KERNELADDR.
This is what vmlinux wants/expects. OTOH, zImage (or any other
program) expects to be loaded into memory where it was linked at.
The code now detects if we're loading a vmlinux or not. If it's a
vmlinux, then yaboot loads the image at KERNELADDR, otherwise it
loads it at the p_vaddr value for each ELF segment.
To detect if we're loading a vmlinux, we look at the e_entry value and
if it is equal to 0xC0000000 for ELF32 or 0xC000000000000000 for ELF64,
then we _assume_ it's a vmlinux.
Peter
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-21 19:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 15:09 [ANN] yaboot maintainer change Benjamin Herrenschmidt
2001-09-20 23:22 ` Ethan Benson
2001-09-21 16:49 ` Peter Bergner
2001-09-21 18:20 ` Tom Rini
2001-09-21 13:29 ` yaboot & zImage's hollis
2001-09-21 18:33 ` Tom Rini
2001-09-21 19:40 ` Peter Bergner [this message]
2001-09-21 21:05 ` Dan Malek
2001-09-21 22:44 ` Tom Rini
2001-09-21 23:22 ` Ethan Benson
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=20010921144050.A223060@brule.borg.umn.edu \
--to=bergner@brule.borg.umn.edu \
--cc=benh@kernel.crashing.org \
--cc=dan@debian.org \
--cc=debian-powerpc@lists.debian.org \
--cc=hollis@austin.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).