From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 7A1ACE00BCC; Fri, 28 Mar 2014 12:09:01 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail1.windriver.com (8.14.5/8.14.5) with ESMTP id s2SJ8tEr014524 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 28 Mar 2014 12:08:56 -0700 (PDT) Received: from [128.224.56.48] (128.224.56.48) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.3.169.1; Fri, 28 Mar 2014 12:08:55 -0700 Message-ID: <5335C8C6.20604@windriver.com> Date: Fri, 28 Mar 2014 15:08:54 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "Hart, Darren" , Richard Purdie References: <1396031047.14790.24.camel@ted> <5335BF1C.9030902@windriver.com> <5335BF6A.8080404@windriver.com> <1396031644.14790.26.camel@ted> <5335C1AF.5080904@windriver.com> <5335C6AA.6020308@windriver.com> In-Reply-To: Cc: yocto-builds , Denys Dmytriyenko , "poky@yoctoproject.org" , "WOLD, SAUL" Subject: Re: meta-yocto-bsp changes and 3.14 X-BeenThere: poky@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Poky build system developer discussion & patch submission for meta-yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Mar 2014 19:09:02 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 14-03-28 03:05 PM, Hart, Darren wrote: > On 3/28/14, 11:59, "Bruce Ashfield" wrote: > >> On 14-03-28 02:57 PM, Hart, Darren wrote: >>> On 3/28/14, 11:38, "Bruce Ashfield" >>> wrote: >>> >>>> On 14-03-28 02:34 PM, Richard Purdie wrote: >>>>> >>>>> >>>>> With regard to beagleboard, whilst the kernel may have support for it, >>>>> I'd like to remove it from meta-yocto-bsp. >>>> >>>> ok. I had planned to just leave the compatible machine as 3.10 and >>>> leave >>>> the support there, since there are a few people who contact me >>>> regularly >>>> and poke with the support. >>>> >>>> Is there a place we can put them as a "retirement" home ? versus asking >>>> people to locally restore the support. >>> >>> The retirement home would be the 1.5 stable releases. Yes? >> >> Nope. That's my point, I have 3.10 changes for the Xm in linux-yocto >> 3.10 that lives in 1.6. We can make it less visible, but I'd like the >> configs to follow the latest versions of the tree. > > Isn't it just the SRCREV that matters here? Those can always just be > applied to 1.5. RP is only asking to remove the beagle board as a > reference BSP from the meta-yocto-bsp layer, he doesn't care if the > linux-yocto/meta data remains in place. We are talking past each other. I'm asking for the meta-yocto-bsp and machine conf file to be around .. somewhere .. I don't want people to have to scrounge them up and revive them from old releases, or revert commits to make them available. So this is outside of linux-yocto, I'd like a single layer than when added, gives access to the BSPs "as they were" in the 3.10 tree, and I'd like that layer to not be on people's local drives only. Bruce > > -- > Darren Hart > Yocto Project - Linux Kernel > Intel Open Source Technology Center > > >