[meta-freescale] The Yocto layer re-architect for FSL QorIQ SDK

Otavio Salvador otavio at ossystems.com.br
Mon Sep 22 07:14:59 PDT 2014


On Mon, Sep 22, 2014 at 10:43 AM, Bob Cochran <yocto at mindchasers.com> wrote:
>
> On 09/22/2014 08:51 AM, Otavio Salvador wrote:
>>
>>
>>
>> On Mon, Sep 22, 2014 at 7:20 AM, zhenhua.luo at freescale.com
>> <mailto:zhenhua.luo at freescale.com> <zhenhua.luo at freescale.com
>> <mailto:zhenhua.luo at freescale.com>> wrote:
>>
>>
>>     __
>>
>>     Following is the structure of the meta-fsl-qoriq layer. __ __
>>
>>     meta-fsl-qoriq____
>>
>>     |--- common                   # the common recipes for QorIQ ARM and
>
>
>
>
> [snip]
>
>
>>     __ __
>>
>>     Can you please review? Your comments and suggestions are welcome.
>>
>>
>> I think it is too soon to talk about any reorganization of the layers. I
>> am still awaiting for the layers cleanup on the meta-fsl-ppc as several
>> recipes there belong to other layers (meta-networking, meta-oe and so on).
>>
>> We also don't have the list of common recipes, so at this moment this is
>> still a guess about the common recipes.
>>
>> LS1 is merged in fsl-arm so you can include it into FSL SDK in your git
>> submodules/supergit/repo file.
>>
>> I see no benefit merging it, just cons ...
>
>
>
> The benefit I see is that it logically groups all QorIQ parts together, which I believe is important.


This does not make sense, sorry. If this would be the case you'd merge
it in OE-Core as you also use GCC, GLibC and so on.

>
> When Freescale needs to provide support for LS2A (next generation) DPAA, the current organization will become a mess.  A lot (if not most) of the QorIQ BSP layer is for DPAA / networking, and I don't think it will make sense to have these duplicated in both meta-fsl-ppc and meta-fsl-arm, or have DPAA code that will be built for the ARM in meta-fsl-ppc (or vice versa).


FSL processors are the ONLY one in the World to provide DPAA? I will
provide two possible routes:

 - If FSL is the only DPAA provider, we make a mets-fsl-dpaa layer
 - If NOT we move DPAA to meta-networking layer where it seems to belong

> I would hope that having this code organized in logical layers under the scope of QorIQ would make it more manageable in migrating from something like a TXXX device to an LS2A device.

I have customers moving from/to TI and FSL, those use meta-ti and
fsl-arm in SAME setup with no issues. It is as easy as change the
machine name.

How users from meta-fsl-ppc will migrated for any new layer layout?
Freescale will break every product layer out there for no good reason,
it seems. The previous repository cannot be removed without critical
impacts.

...

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


More information about the meta-freescale mailing list