From: Darren Hart <dvhart@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
Rick Yang <Rick.Yang@enea.com>
Subject: Re: yocto-kernel-tools
Date: Mon, 07 Jan 2013 08:21:42 -0800 [thread overview]
Message-ID: <50EAF616.5060604@linux.intel.com> (raw)
In-Reply-To: <CADkTA4PNsOqwWbvDmyLGrcn6GVboeFkJX3voR1Pji_FoVU8m1w@mail.gmail.com>
On 12/24/2012 08:15 AM, Bruce Ashfield wrote:
>
>
>
> On Mon, Dec 24, 2012 at 6:28 AM, Rick Yang <Rick.Yang@enea.com
> <mailto:Rick.Yang@enea.com>> 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 <http://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
prev parent reply other threads:[~2013-01-07 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 10:28 yocto-kernel-tools Rick Yang
2012-12-24 16:15 ` yocto-kernel-tools Bruce Ashfield
2013-01-07 16:21 ` Darren Hart [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50EAF616.5060604@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=Rick.Yang@enea.com \
--cc=bruce.ashfield@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.