On Tue, 26 Mar 2013, Brendan Conoboy wrote: > We could create a number of uboot headers. Then after loading the default > uImage, load a separate uboot header overwriting the first 64 bytes of RAM. Please don't engage in those senseless games just to work around a stupid restriction of the uImage file format. If uImage is a problem, just don't use it, period. Problem solved. All the targets supported by the unified kernel are recent enough to have bootz support in their U-Boot source. Please use that. Or, consider the mkimage process as part of the kernel _installation_ procedure and not a pre-distribution step. But if I were you I'd go the bootz route for its simplicity. Nicolas _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
