Dear Aneesh V,
In message 4DDE34C5.1050407@ti.com you wrote:
- I see that size is at offset 0xC in this header. Is this a standard?
- I see that the header is 64 bytes. Is that again a standard for
mkimage.
Both are not really "standards" in the sense that any standardization group like ANSI or IEEE has approved this, but these are standard within U-Boot context. The header (struct image_header) is defined in "include/image.h"
- Is it ok to add u-boot.img to the target "ALL"?
No, because in the general case this is not needed, so it's just a waste of build time and disk space.
- If not, is it ok to add it to "ALL" when CONFIG_SPL is defined?
Something like this:
ifeq ($(CONFIG_SPL),y) .PHONEY : SPL -ALL += SPL +ALL += SPL u-boot.img endif
IN principle this should be OK, but please pay attention not to break out-of-tree builds (You have to prefext target names with "$(obj)").
Is it ok to add support for kernel payload as a subsequent incremental step. That's, right now I intend to parse the mkimage header, find the size and load address and load the image and pass control to it, but *without* passing any parameters. Is that ok?
That's perfectly fine.
Best regards,
Wolfgang Denk