From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2-g21.free.fr (smtp2-g21.free.fr [212.27.42.2]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 48AF1E014F3 for ; Fri, 19 Apr 2013 05:36:09 -0700 (PDT) Received: from e6520eb (pac33-2-82-240-38-71.fbx.proxad.net [82.240.38.71]) (Authenticated sender: eukrea) by smtp2-g21.free.fr (Postfix) with ESMTPSA id 048594B0015; Fri, 19 Apr 2013 14:36:01 +0200 (CEST) Date: Fri, 19 Apr 2013 14:36:00 +0200 From: Eric =?UTF-8?B?QsOpbmFyZA==?= To: Fabio Estevam Message-ID: <20130419143600.49a94116@e6520eb> In-Reply-To: References: <1366311579-29067-1-git-send-email-otavio@ossystems.com.br> <1366311579-29067-3-git-send-email-otavio@ossystems.com.br> <51704ED6.9020300@freescale.com> <20130419100345.5d522189@e6520eb> Organization: =?UTF-8?B?RXVrcsOpYQ==?= Electromatique X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.13; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Cc: meta-freescale Mailing List , Otavio Salvador Subject: Re: [meta-fsl-arm PATCH v2 3/3] linux-fslc: Refactor to use linux-imx.inc and avoid duplication of code X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Apr 2013 12:36:11 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Fabio, Le Fri, 19 Apr 2013 09:26:30 -0300, Fabio Estevam a =C3=A9crit : > On Fri, Apr 19, 2013 at 5:03 AM, Eric B=C3=A9nard wrote: >=20 > > 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. >=20 > Sure, understood. So if we always build uImage as "make uImage > LOADADDR=3D0xxxxx" then it will always work. No matter if you are in a > single machine defconfig or on a multiple machine defconfig. >=20 > What I think it is strange is the need to pass the UBOOT_ENTRYPOINT to > poky and then we need to force "LOADADDR=3D${UBOOT_ENTRYPOINT}" again in > our layer. Why can't poke just always pass > LOADADDR=3D${UBOOT_ENTRYPOINT} itself? If UBOOT_ENTRYPOINT is not passed > then it does the usual "make uImage" method. >=20 because if you look at kernel.bbclass, it's only using UBOOT_LOADADDRESS ?=3D "${UBOOT_ENTRYPOINT}" in=20 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