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

[Eric Bénard]

Hi Fabio,

Le Fri, 19 Apr 2013 09:26:30 -0300,
Fabio Estevam <festevam at gmail.com> a écrit :

> 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.
> 
because if you look at kernel.bbclass, it's only using
UBOOT_LOADADDRESS ?= "${UBOOT_ENTRYPOINT}"
in 
do_uboot_mkimage() {}
which is executed once the kernel is compiled :
addtask uboot_mkimage before do_install after do_compile

So the uImage is generated once the kernel is compiled (without using
make uImage).

So the LOADADDR need is specific to some platforms and not generic
at the oe-core level.

Eric