From: Phil Blundell <pb@pbcl.net>
To: oe-core <openembedded-core@lists.openembedded.org>
Subject: kernels
Date: Fri, 15 Jul 2011 14:21:17 +0100 [thread overview]
Message-ID: <1310736077.3805.37.camel@phil-desktop> (raw)
The other day I was working on a BSP layer for a fairly generic i586
system and I was struck by the fact that we don't appear to have any
vanilla kernel recipes in oe-core. I had sort of expected that, to get
a standard bzImage out, I would just need to ship an appropriate
defconfig in my layer and everything else would "just work".
However, the only kernel that I could immediately find in oe-core was
linux-yocto, which appears to be somewhat more specialized than that
and, at a first glance, looks like it would be better placed in some or
other poky layer than oe-core itself.
Is it the intent that BSP layers are meant to start from linux-yocto and
customise that, or are they expected to provide their own standalone
recipes?
I was also slightly confused by the fragmentary nature of the kernel
helper files. Chasing the references from linux-yocto.bb seems to show
that it includes two .incs and explicitly inherits a total of
six .bbclasses (one of which is, admittedly, blank) and it's not always
entirely obvious what each one is really doing or how they are meant to
interact with each other.
p.
next reply other threads:[~2011-07-15 13:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 13:21 Phil Blundell [this message]
2011-07-15 13:51 ` kernels Bruce Ashfield
2011-07-15 15:02 ` kernels Phil Blundell
2011-07-15 15:36 ` kernels Bruce Ashfield
2011-07-20 15:42 ` kernels Bruce Ashfield
2011-07-20 15:45 ` kernels Koen Kooi
2011-07-20 19:47 ` kernels Bruce Ashfield
2011-07-21 17:23 ` kernels Anders Darander
2011-07-21 17:36 ` kernels Bruce Ashfield
2011-07-21 20:28 ` kernels Anders Darander
2011-08-15 20:52 ` kernels Bruce Ashfield
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=1310736077.3805.37.camel@phil-desktop \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox