From mboxrd@z Thu Jan 1 00:00:00 1970 From: Otavio Salvador Date: Sat, 3 Sep 2016 17:27:01 -0300 Subject: [U-Boot] Building u-boot.imx and SPL simultaneously In-Reply-To: <11f4e24d-17c2-69a6-ba59-078e3bbfe09f@denx.de> References: <226b38f1-0f0f-a997-2272-5bb13d0856bc@jikos.cz> <24f0546a-7a65-45ac-5128-667ff6fb87fa@jikos.cz> <11f4e24d-17c2-69a6-ba59-078e3bbfe09f@denx.de> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Sat, Sep 3, 2016 at 6:40 AM, Stefano Babic wrote: > On 03/09/2016 01:15, Petr Kulhavy wrote: >> You are saying that in order to cover my use case(s) I need two >> defconfigs. Well, ok... >> But how do I integrate this into Buildroot? For the sake of >> maintainability, simplification, reducing chance for an error during >> build I want to have one Buildroot defconfig, run one build command and >> get all the necessary images. >> How do I do that with two U-boot defconfigs? > > I am noit a Buildroot expert, someone else can better point you in the > right direction. I will expect that you need a second target. If I had > to do thuis in Yoct, I will tend to add a new recipe to build .imx variant. On OpenEmbedded-based systems, as is the case of Yocto Project, we introduced the UBOOT_CONFIG mechanism for this. So for example in: https://github.com/Freescale/meta-fsl-arm/blob/master/conf/machine/imx6slevk.conf#L15 The UBOOT_CONFIG is changed, in local.conf for a machine, to: UBOOT_CONFIG = "spinor sd" Both as build. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750