From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Ilya Dmitrichenko <errordeveloper@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Linux kernel recipe template
Date: Mon, 21 Nov 2011 11:08:31 -0500 [thread overview]
Message-ID: <4ECA777F.6070501@windriver.com> (raw)
In-Reply-To: <CAPhDKbHwqW-EA=Dq_32wd1ywE5JmUn9uBqbsurqmeY0RAPce3g@mail.gmail.com>
On 11-11-21 11:01 AM, Ilya Dmitrichenko wrote:
> Hello List,
>
> I have had an attempt to build a kernel from the git sources, trying
> to checkout the v3.1.1 tag, but it appeared to be more difficult then
> I thought. Most of the problem I have had with the yocto-specific
> metadata and some of the extra tasks that it adds. What is the
> cleanest and compatible way to build a kernel from git or any standard
> tree (i.e. 2.6.x or later).
Opinions vary on this point, but if you want to try and use the
yocto kernel tools, add your own meta data and manage the kernel
and follow some of the yocto kernel development workflows .. then
there are compatibility modes and some setup to do what you want.
I also always have a development kernel (currently at 3.2-rc2), if
you need something newer than 3.0.x.
See below for more information.
>
> I can see that the yocto way of building kernel is to provide a commit
> ID for each specific architecture and there also these metadata
> branches, which don't quite understand yet. I managed to somehow slip
> through, but with manual creation of stamp files and manual 'make all
> O=../<build_dir>' stage. I don't seem to find any detailed guide,
> would be great to just see a template in the tree which do just a
> basic build from a given SRC_URI. It would be also nice to have a line
> in this template which would demonstrate how to apply a custom base
> kernel config too.
I have a korg example in poky-extras/meta-kerne-dev/
(git://git.pokylinux.org/poky-extras),
which is intended to show pretty what you were looking for.
I have usecase and documentation requirements for yocto 1.2 for this
example as well, so better references are forthcoming in the not
to distant future.
Cheers,
Bruce
>
> Regards,
prev parent reply other threads:[~2011-11-21 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 16:01 Linux kernel recipe template Ilya Dmitrichenko
2011-11-21 16:08 ` Bruce Ashfield [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=4ECA777F.6070501@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=errordeveloper@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.