From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 5D741E011AF for ; Fri, 7 Sep 2012 09:30:24 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail.windriver.com (8.14.5/8.14.3) with ESMTP id q87GULGH017480 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 7 Sep 2012 09:30:21 -0700 (PDT) Received: from [128.224.146.67] (128.224.146.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.2.309.2; Fri, 7 Sep 2012 09:30:20 -0700 Message-ID: <504A2113.8030100@windriver.com> Date: Fri, 7 Sep 2012 12:30:11 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: Richard Purdie References: <12E1ABCF-B181-4763-88A6-5B7E51758231@gmail.com> <50491060.5030300@balister.org> <50492183.7030101@windriver.com> <5049D8FA.8050600@balister.org> <1347034751.8619.7.camel@ted> In-Reply-To: <1347034751.8619.7.camel@ted> Cc: Yocto Discussion Mailing List , Zhong Hongbo , Vlad Lungu Subject: Re: any success with spartan6-lx9mb? X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Sep 2012 16:30:24 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 12-09-07 12:19 PM, Richard Purdie wrote: > On Fri, 2012-09-07 at 08:27 -0400, Bruce Ashfield wrote: >> On Fri, Sep 7, 2012 at 7:22 AM, Philip Balister wrote: >>> On 09/06/2012 06:19 PM, Bruce Ashfield wrote: > >>>>> >>>>> Speaking of zynq, I have a simple BSP here for the zc702 board: >>>>> >>>>> https://github.com/balister/meta-zynq >>>> >>>> >>>> We have a namespace collision, there is also: >>>> >>>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-zynq/ >>> >>> >>> Before creating the layer I checked: >>> >>> http://www.openembedded.org/wiki/LayerIndex >>> >>> This is where layer information is collected. If a layer is not listed here, >>> yo can expect namespace collisions. >> >> Sure, I don't argue with that, but I wasn't the original owner of the layer so >> I can't say why it was or wasn't put into the wiki .. I'm not really concerned >> about the minor oversight. They layer I pointed to was done under contract >> by xilinx themselves, and contributed to be maintained as a yocto BSP, so >> the layers name is not something that I control or can change. >> >> Other similar layers can use the same name if they want, I was pointing it >> out for reference, since I've had the same thing pointed out to me in >> the past ;) > > The bigger question is whether that layer is getting maintained. If it > isn't, it will likely get removed. I'd prefer it to get added to the > layer index and the namespace collision getting fixed. > > I was going to cc the maintainer but there isn't one listed in the > README which is a really bad start. The feedback I gave when this was > added has not all been acted upon either (multi-dtb.inc, > layencytop/sysprof nastiness). > > This puts it right at the top of my "likely to get removed soon" list. It is being maintained, updates are pending. > > Bruce: Since you have an idea who wrote it, could you find out whether > its going to get fixed (at the very least fix the README, add to the > index and resolve the namespace) or whether I should be deleting it. Don't delete it. Work is being done. This was supposed to be a primary repository for work, and it is the basis for spin off BSPs. There was a handoff issue between Wind River and Xylinx .. but I don't have all the details. And it's something that I'll be carrying forward and pulling kernel patches into linux-yocto on the next kernel bump. I'll do the simple updates to the README and put it in the layer index. Cheers, Bruce > > Cheers, > > Richard > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto