From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <403F9B5C.7010707@embeddededge.com>
Date: Fri, 27 Feb 2004 14:32:44 -0500
From: Dan Malek <dan@embeddededge.com>
MIME-Version: 1.0
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
References: <Iq959772845498.03218@webmail1.inner-21cn.com>	 <1077816291.4242.6.camel@budweiser>	 <Pine.LNX.4.56.0402271730001.24044@mag.sysgo.com>	 <1077834132.4625.2.camel@budweiser>	 <Pine.LNX.4.56.0402271825410.24183@mag.sysgo.com> <1077835127.4625.5.camel@budweiser>
Content-Type: text/plain; charset=us-ascii; format=flowed
Sender: owner-linuxppc-embedded@lists.linuxppc.org
List-Id: <linuxppc-embedded@lists.linuxppc.org>


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/