From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id E9DDFE00724 for ; Mon, 7 Jan 2013 08:21:55 -0800 (PST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 07 Jan 2013 08:20:54 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.84,424,1355126400"; d="scan'208";a="243030076" Received: from envy.jf.intel.com (HELO envy.home) ([10.7.199.53]) by orsmga001.jf.intel.com with ESMTP; 07 Jan 2013 08:21:43 -0800 Message-ID: <50EAF616.5060604@linux.intel.com> Date: Mon, 07 Jan 2013 08:21:42 -0800 From: Darren Hart User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Bruce Ashfield References: <1219DA3ECB038C40A6CF638974AA84A52517920E@sestoex05.enea.se> In-Reply-To: X-Enigmail-Version: 1.4.6 Cc: "yocto@yoctoproject.org" , Rick Yang Subject: Re: yocto-kernel-tools 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: Mon, 07 Jan 2013 16:21:56 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 12/24/2012 08:15 AM, Bruce Ashfield wrote: > > > > On Mon, Dec 24, 2012 at 6:28 AM, Rick Yang > wrote: > > Hi , ____ > > We have a linux release base on yocto, and we want to use > yocto-kernel-tools to manage kernel configuration fragments, instead > of the old method. So we want to know, when poky will use > yocto-kernel-tools to manage the kernel ? Is there a plan? > > > I'm not sure I follow the question. Since yocto 1.0 the kern-tools have > been used > to manage the kernel, they've been changing over time, but the > foundation and > theory is the same. > > If you want to manage a custom kernel, have a look in meta-skeleton for > linux-yocto-custom.bb and you can apply > fragments to any upstream git tree > of your choosing. It would of course be better if we get more > contributions to the > main linux-yocto meta data (yocto-kernel-cache and the linux-yocto meta > branch), but > that's completely voluntary. If you need some documentation on this please let us know, we have some early docs going through some active development we can point you at if interested. -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel