Thanks for the info. But I checked the version supported by the vendor of board does not have bootz command implemented. And I am just a user for UBOOT.
Thus could anyone just let me know that the hack I am using is correct and if I jump at offset 0x40 in uImage then it is equilant of using zImage directly? I use bootm command since it already satisfies all the kernel requirements mentioned at here: http://www.arm.linux.org.uk/developer/booting.php
Best Regards Ritu
On Thu, Mar 21, 2013 at 3:10 AM, Fabio Estevam festevam@gmail.com wrote:
On Wed, Mar 20, 2013 at 6:02 PM, Stephen Warren swarren@wwwdotorg.org wrote:
On 03/20/2013 01:27 PM, Ritu Sharma wrote: ...
I read that uImage is nothing more than (64byte header + zImage). I've
been
studying decompression code so it suited me to tweak UBOOT code to boot zImage rather than writing my own bootcode. Just a small modification in do_bootm_linux function did the job:
In recent versions of U-Boot, you can simply enable the bootz command, which boots a raw zImage.
And in order to enable the bootz command, you need to add: #define CONFIG_CMD_BOOTZ
,in your board config file (include/configs/)