[meta-freescale] [fsl-community-bsp-platform][PATCH] add meta-fsl-ppc layer

[Bob Cochran]

On 08/06/2014 02:08 PM, Otavio Salvador wrote:
> On Wed, Aug 6, 2014 at 2:20 PM, Bob Cochran <yocto at mindchasers.com> wrote:
>> On 07/23/2014 05:28 AM, ting.liu at freescale.com wrote:
>>>
>>> From: Ting Liu <ting.liu at freescale.com>
>>>
>>> Signed-off-by: Ting Liu <ting.liu at freescale.com>
>>> ---
>>>    default.xml | 1 +
>>>    1 file changed, 1 insertion(+)
>>>
>>> diff --git a/default.xml b/default.xml
>>> index a0d85bc..505183a 100644
>>> --- a/default.xml
>>> +++ b/default.xml
>>> @@ -9,6 +9,7 @@
>>>
>>>      <project remote="yocto" revision="master" name="poky"
>>> path="sources/poky"/>
>>>      <project remote="yocto" revision="master" name="meta-fsl-arm"
>>> path="sources/meta-fsl-arm"/>
>>> +  <project remote="yocto" revision="master" name="meta-fsl-ppc"
>>> path="sources/meta-fsl-ppc"/>
>>
>> Still hasn't been applied to master branch?
>
> No; only master-next.


Thank you for the reply Otavio, but I'm not seeing Ting's patch set from 
7/23 that brought meta-fsl-ppc into the Community project.

On 7/23, Ting submitted a set of patches, one was titled 
"[meta-freescale] [meta-fsl-demo][PATCH] add qoriq customized 
packagegroups and images"  that added image and packagegroup recipes 
into the project under meta-fsl-demos.

However, I don't see that any of this (e.g., 
recipes-fsl/images/fsl-image-networking.bb) was applied to either master 
or master-next.



>
>> I see that meta-fsl-ppc has been included in the master-next branch
>> default.xml since 5/22 but specifies the master revision.  I would think we
>> would want to use the master-next revision for the master-next default.xml.
>
> Currently I am not aware of master-next for meta-fsl-ppc so we're
> using the master.
>

There appears to be a master-next branch for meta-fsl-ppc in the Yocto 
Project repo.