[linux-yocto] KERNEL_FEATURES variable, Kernel Configuration Fragments and Kernels other than linux-yocto

Bruce Ashfield bruce.ashfield at windriver.com
Wed Nov 21 08:47:20 PST 2012


On 12-11-21 11:27 AM, Poole, Donald R. wrote:
> Hello All,
>
> I'm currently working on building a custom image for the Raspberry
> Piwith SELinux enabled through the meta-selinux layer, but the layer
> doesn't seem to be able to modify the linux-raspberrypi kernel with the
> SELinux kernel configuration fragment as required. So after doing some
> research on the topic and coming across this thread discussion,
> http://patches.openembedded.org/patch/36315/, it seems that the
> linux-yocto kernel is the only kernel that supports the kernel
> configuration fragment management system and the KERNEL_FEATURES
> variable (Richard Purdie and Saul Wold discuss and mention this toward
> the bottom of the discussion). So, my question is: Is there a timeline
> for opening up the kernel configuration fragment management system to
> work with kernels other than the linux-yocto* kernels? If this
> capability is already available, how would I go about incorporating the
> kernel configuration fragment management system into a kernel other than
> the linux-yocto kernel? I haven
>   't quite figured it out yet, so any assistance would be greatly appreciated.  Thanks in advanced!

Assuming you are working with yocto 1.3 or master, you should just
use the linux-yocto-custom recipes to get configuration fragment
support.

See: meta-skeleton/recipes-kernel/linux/

Using that framework you can point at the git repository of your
choice and start using kernel configuration fragments on top of
a base configuration.

There is one caveat though:

   - KERNEL_FEATURES looks at in-tree configuration fragments at
     the moment, so you'll need to control the addition of your
     fragments via SRC_URI additions versus KERNEL_FEATURES.

     I have a 1.4 feature to extend KERNEL_FEATURES to any linux-yocto-*
     recipe with out of tree meta-data, but it isn't ready yet.

If you end up maintaining your own kernel and branches, you can always
move to an in-tree meta branch and keep more complex meta data and use
the KERNEL_FEATURES without waiting for my 1.4 changes.

Cheers,

Bruce


>
> Donald R. Poole, Jr.
> Research Engineer
> Southwest Research Institute
> _______________________________________________
> linux-yocto mailing list
> linux-yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/linux-yocto
>




More information about the linux-yocto mailing list