[meta-freescale] The updated proposal of FSL Yocto layers reorg - 4-Mar

[Matthew McClintock]

On Fri, Mar 8, 2013 at 6:12 AM, Otavio Salvador <otavio at ossystems.com.br> wrote:
> On Fri, Mar 8, 2013 at 4:04 AM, Luo Zhenhua-B19537 <B19537 at freescale.com> wrote:
>>> -----Original Message-----
>>> From: otavio.salvador at gmail.com [mailto:otavio.salvador at gmail.com] On
>>> Behalf Of Otavio Salvador
>>>
>>> >> >   Following SDK specific layers are maintained in
>>> >> > git.am.freescale.net and git.freescale.com
>>> >> >
>>> >> >     meta-fsl-toolchain: layer for fsl toolchain recipes
>>> >> >
>>> >> >     meta-fsl-multimedia: layer for multimedia SDK
>>> >> >
>>> >> >     meta-fsl-networking: layer for networking SDK
>>> >> >
>>> >> >     meta-fsl-layerscape: layer for layerscape SDK
>>> >>
>>> >> I thought meta-fsl-layerscape would merge with meta-fsl-networking
>>> >> and BSP part to be in meta-fsl-arm (as Vybrid).
>>> > [Luo Zhenhua-B19537] multimedia, networking and layerscape are for
>>> different SDKs specific bits. The common recipes will be put into meta-
>>> fsl-ppc and meta-fsl-arm, including BSP part(e.g. machine conf, u-boot,
>>> kernel, etc). Please elaborate if I don't fully follow your comments.
>>>
>>> I understand now but could you give an example of specific thing which
>>> would go to layerscape layer?
>> [Luo Zhenhua-B19537] what I can imagine is layerscape distro conf file, udev rules of ethernet port rename, demo rootfs image recipes, maybe more...
>
> udev rules can be add to BSP depending on how they're used. However
> all this seems more meta-fsl-networking thingy than a specific SDK.

Why is layerscape a new SDK? Won't it fall under the networking umbrella?

The same images, etc should be generated from the networking SDK. You
can tweak MACHINE_EXTRA_RECOMMENDS type things for different hardware
but that should be minimal and ideally under one umbrella layer.

-M