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

[Bob Cochran]

On 08/07/2014 08:16 AM, Otavio Salvador wrote:
> On Thu, Aug 7, 2014 at 8:07 AM, Bob Cochran <yocto at mindchasers.com> wrote:
>>
>> 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.
>
> Yes. The meta-fsl-demos bits has not been merged. Those still require
> more work and to be sincere adding the images and packagegroups need
> to come with a good thinking how to do it as we always need to avoid
> too many images with close content and like.
>
> Our main focus now is in clean up meta-fsl-ppc so it can be enabled in master.


Right, I'm starting to test meta-fsl-ppc this week live on a t1040rdb. 
I was using my own image & package group but since I'm finding some 
issues, I would like to use Ting's provided demo image & package groups 
as a common baseline before I report any findings or maybe submit a patch.

I'll just continue to test with Ting's community related patches applied 
in my own development branch(es) & not worry about using repo.

However, this obviously makes it a little messy when worrying about 
whether we're all testing with the same commits on the various layers.

I'm definitely looking forward to the future & getting in sync with the 
entire community.

Thanks

Bob


>
>>>> 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.
>
> They point to same hash for now. So we're fine. Please prepare  a
> patch to change it for master-next in master-next manifest.
>