From: Dan Malek <dan@embeddededge.com>
To: Bob Beck <beck@assurtech.com>
Cc: mgroeger@sysgo.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: ADS860 - unable to load kernel- Bad magic number
Date: Fri, 27 Feb 2004 14:32:44 -0500 [thread overview]
Message-ID: <403F9B5C.7010707@embeddededge.com> (raw)
In-Reply-To: 1077835127.4625.5.camel@budweiser
Bob Beck wrote:
> Thanks. What is the difference between zImage.embedded and vmlinux.gz
> generated by the kernel build ?
Huge. The vmlinux.gz is just the gzipped kernel. The zImage contains
the 'bootloader' code that can perform some processor initialization,
uncompresses the vmlinux.gz, locates it properly in memory, sets initial
registers, then jumps to the start of the kernel.
> This is the file used by U-Boot's mkImage command to produce a
> vmlinux.img file.
If you are building for u-boot, you should 'make uImage' and use
the uImage that is created.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-27 19:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Iq959772845498.03218@webmail1.inner-21cn.com>
2004-02-26 17:24 ` ADS860 - unable to load kernel- Bad magic number Bob Beck
2004-02-27 16:32 ` Marius Groeger
2004-02-26 22:22 ` Bob Beck
2004-02-27 17:29 ` Marius Groeger
2004-02-26 22:38 ` Bob Beck
2004-02-27 19:32 ` Dan Malek [this message]
2004-02-27 1:32 ` Bob Beck
2004-02-27 21:05 ` Dan Malek
2004-03-01 22:58 ` Booting Linux on a Custom PPC Board Bob Beck
2004-03-02 23:51 ` Wolfgang Denk
2004-03-02 17:45 ` Bob Beck
2004-02-27 4:34 ADS860 - unable to load kernel- Bad magic number m.venkatraj
2004-02-27 4:45 ` John Zhou
2004-02-27 8:07 ` song sam
-- strict thread matches above, loose matches on Subject: below --
2004-02-27 8:27 Demke, Torsten
2004-02-27 9:14 m.venkatraj
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=403F9B5C.7010707@embeddededge.com \
--to=dan@embeddededge.com \
--cc=beck@assurtech.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mgroeger@sysgo.com \
/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).