[U-Boot] [PATCH v2 18/22] armv7: embed u-boot size within u-boot for use from SPL
Wolfgang Denk
wd at denx.de
Thu May 26 19:21:01 CEST 2011
Dear Aneesh V,
In message <4DDE34C5.1050407 at ti.com> you wrote:
>
> 1. I see that size is at offset 0xC in this header. Is this a standard?
> 2. 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"
> 3. 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.
> 4. 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
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Due to lack of disk space, this fortune database has been discontinued.
More information about the U-Boot
mailing list