summaryrefslogtreecommitdiff
path: root/meta/recipes-kernel/oprofile/oprofileui
diff options
context:
space:
mode:
authorDarren Hart <dvhart@linux.intel.com>2011-07-25 11:10:17 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-08-12 17:16:59 +0100
commitbafaaad264fe3e745c714951ddcf2784d33b755a (patch)
treecb475094cdc455d46cf0148f0ddb7046c9407bd7 /meta/recipes-kernel/oprofile/oprofileui
parent92aa6a587f4fabfadbebdb7ae24306d36f43910a (diff)
downloadopenembedded-core-bafaaad264fe3e745c714951ddcf2784d33b755a.tar.gz
openembedded-core-bafaaad264fe3e745c714951ddcf2784d33b755a.tar.bz2
openembedded-core-bafaaad264fe3e745c714951ddcf2784d33b755a.tar.xz
openembedded-core-bafaaad264fe3e745c714951ddcf2784d33b755a.zip
Move meta-rt recipes to oe-core (meta)
Keeping the rt recipes in their own layer has led to maintenance issues, particularly with the linux-yocto-rt recipes. As these kernel types are part of the same linux-yocto source repository, it seems reasonable to include the rt kernel recipes alongside the standard recipes. A new recipes-rt directory for the other recipes provides adequate separation and eliminates the need for a separate layer. As there is no meta-rt/conf/layer.conf to force the kernel, users must now specify the rt kernel in their local.conf or in the machine.conf: PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt" The merging of the rt recipes into the core also eliminates complications with multiple layer dependencies for new BSP layers. Having to either separate RT BSPs from standard BSPs or force users to add meta-rt to bblayers even when not building an RT BSP (because the RT BSPs in the same layer would fail to parse without it) was sub-optimal at best. Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Diffstat (limited to 'meta/recipes-kernel/oprofile/oprofileui')
0 files changed, 0 insertions, 0 deletions