On Fri, Apr 19, 2013 at 5:03 AM, Eric Bénard <[email protected]> wrote:
> maybe most defconfig support only one machine when those in
> meta-fsl-arm support several machines sometimes with different LOADADDR
> requirements and thus need the precision to get a working kernel on a
> specific platform at compile time.
Sure, understood. So if we always build uImage as "make uImage
LOADADDR=0xxxxx" then it will always work. No matter if you are in a
single machine defconfig or on a multiple machine defconfig.
What I think it is strange is the need to pass the UBOOT_ENTRYPOINT to
poky and then we need to force "LOADADDR=${UBOOT_ENTRYPOINT}" again in
our layer. Why can't poke just always pass
LOADADDR=${UBOOT_ENTRYPOINT} itself? If UBOOT_ENTRYPOINT is not passed
then it does the usual "make uImage" method.
We could call it OUR_UBOOT_ENTRYPOINT instead and use this
OUR_UBOOT_ENTRYPOINT in our layer, no?
Or maybe in the next release we could just switch to zImage and no
need to worry about such things ;-)
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale
