From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id E5B2FE00781; Thu, 7 Aug 2014 12:03:57 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from smtp.webfaction.com (mail6.webfaction.com [74.55.86.74]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id B07FDE0034B for ; Thu, 7 Aug 2014 12:03:49 -0700 (PDT) Received: from [192.168.1.10] (c-68-38-40-177.hsd1.nj.comcast.net [68.38.40.177]) by smtp.webfaction.com (Postfix) with ESMTP id 0FBF82279061; Thu, 7 Aug 2014 19:03:47 +0000 (UTC) Message-ID: <53E3CD92.4060607@mindchasers.com> Date: Thu, 07 Aug 2014 15:03:46 -0400 From: Bob Cochran User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Otavio Salvador References: <1406107717-19828-1-git-send-email-ting.liu@freescale.com> <1406107717-19828-2-git-send-email-ting.liu@freescale.com> <53E263DA.3000803@mindchasers.com> <53E35DE9.6060906@mindchasers.com> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" Subject: Re: [fsl-community-bsp-platform][PATCH] add meta-fsl-ppc layer X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Aug 2014 19:03:58 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 08/07/2014 08:16 AM, Otavio Salvador wrote: > On Thu, Aug 7, 2014 at 8:07 AM, Bob Cochran wrote: >> >> On 08/06/2014 02:08 PM, Otavio Salvador wrote: >>> >>> On Wed, Aug 6, 2014 at 2:20 PM, Bob Cochran wrote: >>>> >>>> On 07/23/2014 05:28 AM, ting.liu@freescale.com wrote: >>>>> >>>>> >>>>> From: Ting Liu >>>>> >>>>> Signed-off-by: Ting Liu >>>>> --- >>>>> 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 @@ >>>>> >>>>> >>>> path="sources/poky"/> >>>>> >>>> path="sources/meta-fsl-arm"/> >>>>> + >>>> 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. >