From: "Akhilesh Soni" <akhilesh@innomedia.soft.net>
To: <linuxppc-embedded@ozlabs.org>
Subject: Difference between zImage.treeboot zImage
Date: Sat, 26 Aug 2006 10:22:16 +0530 [thread overview]
Message-ID: <005601c6c8cb$67bc0750$0a12a8c0@innomedia> (raw)
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
Hi,
I'm using opebios on IBM redwood6 ppc405 platform. Currently when I compile my kernel by doing "make zImage" I get one file zImage.treeboot. I just want to know what is the difference between normal zImage and zImage.treeboot.
One more thing I've noticed that there is also a small boot program inside the kernel also (arch/ppc/boot/simple) which decompresses the kernel and jumps to start of zImage. Why this is required ? In normal U-boot which I've worked earlier directly decompresses the zImage by bootm command and starts its execution. Please help me in understanding this mechanism.
Also If I want to build linux kernel 2.6 then will my opebios will work with it or I'll have to change to uboot for for 2.6 kernel.
regards,
Akhilesh
[-- Attachment #2: Type: text/html, Size: 1594 bytes --]
reply other threads:[~2006-08-26 4:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='005601c6c8cb$67bc0750$0a12a8c0@innomedia' \
--to=akhilesh@innomedia.soft.net \
--cc=linuxppc-embedded@ozlabs.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).