[U-Boot] Bad Linux ARM zImage magic

Due to this patch: 0001-omap3_beagle-uEnv.txt-bootz-n-fixes.patch, u-boot for my beagleboard seems to need always a zImage. Up to now, I used uImage just fine. Questions: - Can I convert vmLinux or uImage in to the required zImage? - Is it possible to use bitbake (I’m using the Angstrom 3.28 kernel) to create a zImage instead of uImage? - Can I just replace the part "loaduimagefat=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} zImage\0" With "loaduimagefat=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} uImage\0" In omap3_beagle.h to get the previously working behaviour?

On Tue, Oct 22, 2013 at 11:11 PM, claus anders cytronimei@yahoo.de wrote:
Due to this patch: 0001-omap3_beagle-uEnv.txt-bootz-n-fixes.patch, u-boot for my beagleboard seems to need always a zImage. Up to now, I used uImage just fine.
Correct, that's exactly one of the features that my out of tree patch does.. If you'd like to use uImage, don't apply my patch. ;)
(adding u-boot cc this time..)
Regards,
participants (2)
-
claus anders
-
Robert Nelson