[meta-freescale] [PATCH 1/3] u-boot-cm-fx6: add u-boot configuration for cm-fx6 machines

[Otavio Salvador]

Hello Igor,

On Tue, Apr 14, 2015 at 3:05 PM, Igor Grinberg <grinberg at compulab.co.il> wrote:
> On 04/13/15 16:35, Otavio Salvador wrote:
>> Hello Valentin,
>> Hello Igor,
>>
>> On Sat, Apr 11, 2015 at 6:39 AM, Valentin Raevsky
>> <valentin at compulab.co.il> wrote:
>>> Add u-boot configuration for cm-fx6 machines.
>>> This is a fork of the mainline u-boot with the CompuLab patches on top.
>>>
>>> Signed-off-by: Valentin Raevsky <valentin at compulab.co.il>
>>
>> The U-Boot recipe is very good. The only remark I believe could be
>> addressed would be to name it u-boot-compulab so it does not sounds to
>> be machine specific and you have extend it for other machines/sbc/som
>> in future.
>
> I'm not sure I understand this.
> Suppose, we have several Freescale SoC based machines, using different
> U-Boot versions from different repositories.
> How should the recipe be structured/build for such configurations?
> Or is it assumed that all the boards are supported by the same
> repository/mainline?

In this specific case I would expect one recipe per version, let's say:

u-boot-compulab_2014.04.bb
u-boot-compulab_2015.04.bb

However I think from CompuLab perspective it is easier if all share
same U-Boot version. We for example provide U-Boot 2015.04[1] for all
(but i.MX6SoloX SabreAUTO) reference boards plus a good amount of 3rd
party boards.

1. http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/recipes-bsp/u-boot/u-boot-fslc_2015.04.bb?h=fido

I don't think you'll end with one U-Boot tree per board, it will be a
maintenance nightmare.

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