[meta-freescale] Does anybody know of a quick way to migrate an IMX6 BSP from dora to daisy?

Eric Nelson eric.nelson at boundarydevices.com
Fri Jun 20 14:18:45 PDT 2014

Hi Stephen,

On 06/20/2014 12:31 PM, Stephen Munnings wrote:
> -----Original Message-----
> From: Fabio Estevam [mailto:festevam at gmail.com] 
> Sent: Friday, June 20, 2014 2:17 PM
> To: Otavio Salvador
> Cc: Stephen Munnings; meta-freescale at yoctoproject.org
> Subject: Re: [meta-freescale] Does anybody know of a quick way to migrate an IMX6 BSP from dora to daisy?
> On Fri, Jun 20, 2014 at 2:18 PM, Otavio Salvador <otavio at ossystems.com.br> wrote:
>> During the change, we (U-Boot community) ported all boards in the 
>> source code but as you keep your board in an internal fork you need to 
>> handle it yourself.
> Tha's correct. In order to avoid such pain in the future, Stephen could add his board support to mainline U-boot.
> This way, whenever an API change happens, the board will be automatically converted.
> -----End Original Message-----
> Thanks Fabio and Otavio.
> Even if we were going to put this board in the mainline U-boot
> (somewhat unlikely, as the board itself is a sub-component of a larger
> system, and not likely to ever hit the market as the "board by itself"),
> it was (and still is) under development. I don't think it is very wise
> (if it is even allowed) to put an unfinished board into the U-boot mainline.
> The only issues I have here are:
> a) The lack of notification that such a change had happened between
> dora and daisy. And I don’t see how I can blame anybody for that, as I
>  am not sure how that information should/would/could have been sent to
> the right target audience in the appropriate time frame(s) anyway.
> Timely responses to my query (which did happen) are sufficient, I think.
> b) The lack of the "conversion tool". Apparently Eric Nelson of
> Boundary Devices did much of this work (thanks Eric <genuine> ), but the
> conversion tool seems to have "gone missing". That would have solved
> everything in a reasonably cost effective manner. A pity it is MIA!

This script was kind of a glorified search and replace, and if you're
just updating one board, doing this by hand is tedious but not very
time consuming.

> For now, we will just stay with dora, and 2013.10. At least we will
> now know some of the costs associated with moving forward if we ever
> need to.

I do think you're missing something. The pad changes I made were to
U-Boot, and there's no reason you can't stick with your 2013.10
version of U-Boot and migrate to a 3.10.17 kernel.

Changing the kernel is likely much more involved, since you should
switch to device-tree in the process, and no amount of tool helps there.

Your best bet is to closely track your differences from another board
that's already made the jump.

This is essentially what we do with our 20-some-odd custom boards
that tend to be variants of SABRE Lite/Nitrogen6x designs.



More information about the meta-freescale mailing list