[meta-freescale] [meta-fsl-arm PATCH v2 3/3] linux-fslc: Refactor to use linux-imx.inc and avoid duplication of code

[Otavio Salvador]

On Fri, Apr 19, 2013 at 9:26 AM, Fabio Estevam <festevam at gmail.com> wrote:
> On Fri, Apr 19, 2013 at 5:03 AM, Eric Bénard <eric at eukrea.com> 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.

It'd not be need if we had KEEPUIMAGE as 'no' Yocto would generate it
without the workaround but we'd end generation two images.

> 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 ;-)

Yes, this would be an option as well ;-)

--
Otavio Salvador                             O.S. Systems
E-mail: otavio at ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br