From: Darren Hart <dvhart@linux.intel.com>
To: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: kernel type selection
Date: Tue, 14 Dec 2010 12:59:36 -0800 [thread overview]
Message-ID: <4D07DAB8.3030504@linux.intel.com> (raw)
In developing new kernel recipes, I've run across some difficulty in
determining the ideal way to select one kernel recipe over another. The
machine configs specify the preferred provider. For the Linaro layer, I
setup new machine configs which specified the linux-linaro as the
preferred kernel.
As I'm working with preempt_rt, I'm running into this again. I could
create more machine configs, but this approach won't scale well (having
to create a copy of all the supported machine configs just to change the
preferred kernel). I could set LINUX_KERNEL_TYPE="preempt_rt" in my
local.conf, but that would reuse all the settings in the existing
recipes (like COMPATIBLE_MACHINES), all of which don't necessary apply
to the new kernel type.
I've considered looking for a way to specify the kernel type in the new
image definitions (ie poky-image-rt) and creating new recipes for each
kernel type. I like the idea of one recipe per kernel type as this makes
things more explicit and avoids contamination between the various kernel
types. This approach however seems to be at odds with the Poky way of
doing this which, as I understand it, would be to specify the provider
in the machine config and any modifiers (like type) in the local.conf.
Can we get a discussion started here to determine some best practices?
Thanks,
--
Darren Hart
Yocto Linux Kernel
next reply other threads:[~2010-12-14 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 20:59 Darren Hart [this message]
2010-12-20 5:08 ` kernel type selection Bruce Ashfield
2010-12-20 18:15 ` Darren Hart
2010-12-20 21:19 ` Khem Raj
2010-12-21 3:24 ` Bruce Ashfield
2010-12-21 4:20 ` Darren Hart
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=4D07DAB8.3030504@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=poky@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.