On Fri, Apr 19, 2013 at 9:38 AM, Daiane Angolini <[email protected]> wrote: > On 04/19/2013 09:36 AM, Eric Bénard wrote: >> >> Hi Fabio, >> >> Le Fri, 19 Apr 2013 09:26:30 -0300, >> Fabio Estevam <[email protected]> a écrit : >> >>> 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. >>> >> 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 >> > > And, if you follow what happens when our kernel is built, you will see that > uboot_mkimage is never called
As I said, because KEEPUIMAGE is 'yes' so it is supposed to keep the uImage generated during kernel build. -- Otavio Salvador O.S. Systems E-mail: [email protected] http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
