Re: A question on adding a new program to a new meta layer

[Darren Hart <dvhart@linux.intel.com>]

On 03/07/2013 06:04 AM, Bruce Ashfield wrote:
> On 13-03-07 12:05 AM, Insop Song wrote:
>> Bruce,
>>
>> That's very good. I will bring linux-yocto-3.8 kernel to meta-dl.
>> (https://github.com/insop/meta-dl/tree/linux-yocto-3.8)
> 
> I have another suggestion to offer here, one I've been wanting to
> do for a bit.
> 
> I've added Darren Hart to the thread, since I'd like to hear from
> him on this as well.
> 
> I have a use for the scheduling tools and benchmark cases for some
> virtualization usecases (meta-virtualization on git.yoctoproject.org).
> 
> We already have "recipes-rt" in oe-core, and the preempt-rt kernel
> available from linux-yocto, and as we've been discussing I've added
> support for EDF/sched_dealine in linux-yocto-3.8.
> 
> I'm not a fan of having to many layers, but rather than putting these
> efforts in github layers, hiding them in meta-virtualiation and they
> aren't yet "core" enough to go in oe-core .. I'd rather see them
> conslidated in a "meta-realtime" (or whatever name we decide on)
> layer on git.yoctoproject.org.


I'm fine with that. We should probably consider adding a realtime distro
definition as well at some point soon.


> 
> There are also ideas around interrupt management, AMP, and alternative
> system partitioning that I'd like to drive into such a layer.
> 
> A quick scan of the layer index, doesn't show anything that matches
> this description. So I'm suggesting that we create a new layer
> to consolidate these approaches, and a layer that can be consumed by
> some of the other layers that are currently in progress.
> 
> Comments ? In particular, point out a layer that already does this that
> I've missed.


No objection. Something outside of core would be better do to the
experimental nature of so much of this stuff.


-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel