[meta-freescale] FSL Community BSP Meeting - 07/03/2014 - 18:00 GMT

[Bob Cochran]

On 06/27/2014 09:55 AM, Otavio Salvador wrote:
> meta-fsl-ppc
> * Release Notes
> * Technical implications



Hello FSL BSL Community.

This is the first of 2 emails that I am forwarding from earlier 
discussions regarding meta-fsl-ppc.

I have periodically used the meta-freescale board to raise issues that I 
see about the disconnect between FSL's use of the Yocto Project repo, 
their public GIT, and the SDK releases and a general lack of 
transparency regarding their BSP / SDK development and bug resolution 
process.

I hope these issues can be followed and worked in upcoming BSP meetings.

Bob


-------- Original Message --------
Subject: RE: Re:[mcswdev] [yocto] Yocto branches policy for concurrent 
SDK releases
Date: Thu, 23 Jan 2014 05:39:07 +0000
From: zhenhua.luo at freescale.com <zhenhua.luo at freescale.com>
To: Bob Cochran <yocto at mindchasers.com>
CC: yocto at yoctoproject.org <yocto at yoctoproject.org>

Hi Bob,

Sorry for the late response.

 > -----Original Message-----
 > From: Bob Cochran [mailto:yocto at mindchasers.com]
 > Sent: Friday, January 10, 2014 4:25 AM
 >
 > Any plans to create a repo for meta-fsl-networking on git.yoctoproject
 > for Power / QorIQ developers?
[Luo Zhenhua-B19537] meta-fsl-networking layer manages the packages 
maintained internally, so the layer can't be upstreamed.

 > It would be good for yocto users, such as myself, to be able to build
 > something incremental between the SDK releases using updated / patched
 > recipes pulled from the yocto repos, which should include meta-fsl-
 > networking.
 >
 > Say I wanted to propose a patch to a recipe like fsl-image-full, which is
 > in meta-fsl-networking, how would I go about it?
[Luo Zhenhua-B19537] For such case, we will consider to move the demo 
image recipes into meta-fsl-ppc layer.

 > Last February (2013), you proposed an FSL Yocto layers reorg that merged
 > layerscape/ARM with Power for QorIQ.  I imagine you're getting close to
 > having something internally.  Can you please share the vision with us
 > along with whether it will be public on the yocto project (as opposed to
 > kept under wraps with incremental SDK releases)?
[Luo Zhenhua-B19537] Currently we are working on it, and will publish 
the staffs publicly when it is ready.


Best Regards,

Zhenhua