From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx-3.enea.com (sestofw01.enea.se [192.36.1.252]) by yocto-www.yoctoproject.org (Postfix) with SMTP id 290C8E01471 for ; Mon, 24 Dec 2012 02:28:43 -0800 (PST) Received: from SESTOEX05.enea.se ([fe80::41cb:8d2e:2e90:a183]) by SESTOEX08.enea.se ([fe80::fda4:d8b2:80c9:b320%24]) with mapi id 14.02.0318.001; Mon, 24 Dec 2012 11:28:41 +0100 From: Rick Yang To: "yocto@yoctoproject.org" Thread-Topic: yocto-kernel-tools Thread-Index: Ac3hu4GJAAZp9A67RHawSu/7jtnXmA== Date: Mon, 24 Dec 2012 10:28:40 +0000 Message-ID: <1219DA3ECB038C40A6CF638974AA84A52517920E@sestoex05.enea.se> Accept-Language: sv-SE, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.214.58] MIME-Version: 1.0 Subject: 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, 24 Dec 2012 10:28:44 -0000 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_1219DA3ECB038C40A6CF638974AA84A52517920Esestoex05enease_" --_000_1219DA3ECB038C40A6CF638974AA84A52517920Esestoex05enease_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi , We have a linux release base on yocto, and we want to use yocto-kernel-tool= s to manage kernel configuration fragments, instead of the old method. So w= e want to know, when poky will use yocto-kernel-tools to manage the kernel = ? Is there a plan? Thanks! Rick --_000_1219DA3ECB038C40A6CF638974AA84A52517920Esestoex05enease_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi ,

We have a linux release base on yocto, and we want t= o 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-tool= s to manage the kernel ? Is there a plan?

 

Thanks!

 

Rick

 

 

--_000_1219DA3ECB038C40A6CF638974AA84A52517920Esestoex05enease_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-la0-f42.google.com (mail-la0-f42.google.com [209.85.215.42]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 37156E006B4 for ; Mon, 24 Dec 2012 08:15:55 -0800 (PST) Received: by mail-la0-f42.google.com with SMTP id s15so8812869lag.15 for ; Mon, 24 Dec 2012 08:15:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/EvCyESeD6js4N8eVR6lATu2SXMU4pM9UPzNPsp1xW4=; b=SgtaeHkdDA0ZySJ4+79qTRqMO0iELk2F2zAVQdm5Qf98+VioEu6BxN3x0tj0M7PSg9 PZHySjHnms7iAFW2oGJ7GSyuRTLSZfO9n5oQ0/E/gE8Zyk6jZX6wjo2Dpjr2V6tYzKqS pMioYvfHmBD5WLb20GHZc+QQFUexGiHjDD7bLB0yIJkwwGj+5yl4xUDUO4WmEWSdGrl5 gnsqI+AabF0VNJG7IImsprx57ty+2ATDUPTg59rkc06/QT47qEzCEmmu/s9TdOi1qnKh J512tKSMxHbGX30qrd6fDuCO9fR+X/wzxgSZArxcsXf7PVsMoekg9JqrXX9+Rm3J6I5J EvuQ== MIME-Version: 1.0 Received: by 10.112.87.104 with SMTP id w8mr8997354lbz.49.1356365753687; Mon, 24 Dec 2012 08:15:53 -0800 (PST) Received: by 10.112.127.35 with HTTP; Mon, 24 Dec 2012 08:15:53 -0800 (PST) In-Reply-To: <1219DA3ECB038C40A6CF638974AA84A52517920E@sestoex05.enea.se> References: <1219DA3ECB038C40A6CF638974AA84A52517920E@sestoex05.enea.se> Date: Mon, 24 Dec 2012 12:15:53 -0400 Message-ID: From: Bruce Ashfield To: Rick Yang Cc: "yocto@yoctoproject.org" 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, 24 Dec 2012 16:15:55 -0000 Content-Type: multipart/alternative; boundary=bcaec554e0f6ef1f6304d19b823b --bcaec554e0f6ef1f6304d19b823b Content-Type: text/plain; charset=ISO-8859-1 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. Cheers, Bruce > **** > > ** ** > > Thanks!**** > > ** ** > > Rick**** > > ** ** > > ** ** > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" --bcaec554e0f6ef1f6304d19b823b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Mon, Dec 24, 2012 at 6:28 AM, Rick Yang <Rick.Yang@enea.com> wrote:

Hi ,

We have a linux release base on yocto, and we want t= o 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-tool= s 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, b= ut the foundation and
theory is the same.

If you = want to manage a custom kernel, have a look in meta-skeleton for=A0
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 co= ntributions to the
main linux-yocto meta data (yocto-kernel= -cache and the linux-yocto meta branch), but
that's com= pletely voluntary.=A0

Cheers,

Bruce
=A0

=A0

Thanks!

=A0

Rick

=A0

=A0


_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto




--
"Th= ou shalt not follow the NULL pointer, for chaos and madness await thee at i= ts end"
--bcaec554e0f6ef1f6304d19b823b-- 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