Patchwork [fsl-community-bsp-platform] add meta-fsl-ppc layer

login
register
mail settings
Submitter Ting Liu
Date July 23, 2014, 9:28 a.m.
Message ID <1406107717-19828-2-git-send-email-ting.liu@freescale.com>
Download mbox | patch
Permalink /patch/76473/
State Not Applicable
Delegated to: Otavio Salvador
Headers show

Comments

Ting Liu - July 23, 2014, 9:28 a.m.
From: Ting Liu <ting.liu@freescale.com>

Signed-off-by: Ting Liu <ting.liu@freescale.com>
---
 default.xml | 1 +
 1 file changed, 1 insertion(+)
Daiane Angolini - July 23, 2014, 2:23 p.m.
On Wed, Jul 23, 2014 at 6:28 AM,  <ting.liu@freescale.com> wrote:
> From: Ting Liu <ting.liu@freescale.com>


I was expecting in this commit log a triumphal long and emotional
history on how and why meta-fsl-pcc is taking his part in this
community project.

Do you really prefer to be simple in this historical moment?

Daiane
>
> Signed-off-by: Ting Liu <ting.liu@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"/>
>
>    <project remote="oe" revision="master" name="meta-openembedded" path="sources/meta-openembedded"/>
>
> --
> 1.8.3.2
>
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
Bob Cochran - July 24, 2014, 4:41 a.m.
On 07/23/2014 10:23 AM, Daiane Angolini wrote:
> On Wed, Jul 23, 2014 at 6:28 AM,  <ting.liu@freescale.com> wrote:
>> From: Ting Liu <ting.liu@freescale.com>
>
>
> I was expecting in this commit log a triumphal long and emotional
> history on how and why meta-fsl-pcc is taking his part in this
> community project.
>
> Do you really prefer to be simple in this historical moment?


Some of you may be interested to know that I was able to apply all of 
Ting's patches today, perform a repo sync, which pulled down 
meta-fsl-ppc master into fsl-community-bsp/sources, and build 
fsl-image-networking from meta-fsl-demos for my t1040rdb-64b machine 
without error.

I thought this was great news.  Thank you very much Ting!

I think I'll have some time to test it a little tomorrow.


>
> Daiane
>>
>> Signed-off-by: Ting Liu <ting.liu@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"/>
>>
>>     <project remote="oe" revision="master" name="meta-openembedded" path="sources/meta-openembedded"/>
>>
>> --
>> 1.8.3.2
>>
>> --
>> _______________________________________________
>> meta-freescale mailing list
>> meta-freescale@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale
Zhenhua Luo - July 24, 2014, 9:38 a.m.
Thank you, Bob. 

> -----Original Message-----
> From: meta-freescale-bounces@yoctoproject.org [mailto:meta-freescale-
> bounces@yoctoproject.org] On Behalf Of Bob Cochran
> Sent: Thursday, July 24, 2014 12:41 PM
> To: meta-freescale@yoctoproject.org
> Subject: Re: [meta-freescale] [fsl-community-bsp-platform][PATCH] add
> meta-fsl-ppc layer
> 
> On 07/23/2014 10:23 AM, Daiane Angolini wrote:
> > On Wed, Jul 23, 2014 at 6:28 AM,  <ting.liu@freescale.com> wrote:
> >> From: Ting Liu <ting.liu@freescale.com>
> >
> >
> > I was expecting in this commit log a triumphal long and emotional
> > history on how and why meta-fsl-pcc is taking his part in this
> > community project.
> >
> > Do you really prefer to be simple in this historical moment?
> 
> 
> Some of you may be interested to know that I was able to apply all of
> Ting's patches today, perform a repo sync, which pulled down meta-fsl-ppc
> master into fsl-community-bsp/sources, and build fsl-image-networking
> from meta-fsl-demos for my t1040rdb-64b machine without error.
> 
> I thought this was great news.  Thank you very much Ting!
> 
> I think I'll have some time to test it a little tomorrow.
> 
> 
> >
> > Daiane
> >>
> >> Signed-off-by: Ting Liu <ting.liu@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"/>
> >>
> >>     <project remote="oe" revision="master" name="meta-openembedded"
> >> path="sources/meta-openembedded"/>
> >>
> >> --
> >> 1.8.3.2
> >>
> >> --
> >> _______________________________________________
> >> meta-freescale mailing list
> >> meta-freescale@yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/meta-freescale
> 
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
Bob Cochran - Aug. 6, 2014, 5:20 p.m.
On 07/23/2014 05:28 AM, ting.liu@freescale.com wrote:
> From: Ting Liu <ting.liu@freescale.com>
>
> Signed-off-by: Ting Liu <ting.liu@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?

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.

I have been away for a few days, so the gears are slowly starting to 
roll again.  Please excuse me if this has been discussed recently, but 
I'm just not seeing it in the mail lists.


>
>     <project remote="oe" revision="master" name="meta-openembedded" path="sources/meta-openembedded"/>
>
>
Otavio Salvador - Aug. 6, 2014, 6:08 p.m.
On Wed, Aug 6, 2014 at 2:20 PM, Bob Cochran <yocto@mindchasers.com> wrote:
> On 07/23/2014 05:28 AM, ting.liu@freescale.com wrote:
>>
>> From: Ting Liu <ting.liu@freescale.com>
>>
>> Signed-off-by: Ting Liu <ting.liu@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.

> 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.
Bob Cochran - Aug. 7, 2014, 11:07 a.m.
On 08/06/2014 02:08 PM, Otavio Salvador wrote:
> On Wed, Aug 6, 2014 at 2:20 PM, Bob Cochran <yocto@mindchasers.com> wrote:
>> On 07/23/2014 05:28 AM, ting.liu@freescale.com wrote:
>>>
>>> From: Ting Liu <ting.liu@freescale.com>
>>>
>>> Signed-off-by: Ting Liu <ting.liu@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.
Otavio Salvador - Aug. 7, 2014, 12:16 p.m.
On Thu, Aug 7, 2014 at 8:07 AM, Bob Cochran <yocto@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@mindchasers.com> wrote:
>>>
>>> On 07/23/2014 05:28 AM, ting.liu@freescale.com wrote:
>>>>
>>>>
>>>> From: Ting Liu <ting.liu@freescale.com>
>>>>
>>>> Signed-off-by: Ting Liu <ting.liu@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.

>>> 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.
Bob Cochran - Aug. 7, 2014, 7:03 p.m.
On 08/07/2014 08:16 AM, Otavio Salvador wrote:
> On Thu, Aug 7, 2014 at 8:07 AM, Bob Cochran <yocto@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@mindchasers.com> wrote:
>>>>
>>>> On 07/23/2014 05:28 AM, ting.liu@freescale.com wrote:
>>>>>
>>>>>
>>>>> From: Ting Liu <ting.liu@freescale.com>
>>>>>
>>>>> Signed-off-by: Ting Liu <ting.liu@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.
>

Patch

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"/>
 
   <project remote="oe" revision="master" name="meta-openembedded" path="sources/meta-openembedded"/>