Selecting different kernel inside an image recipe
Hello list,
I'm trying to build variantions/brands of an image that only differ in kernel configuration and kernel modules included, but everything else stays the same, for the exact same board, as in the main image.
Setting PREFERRED_PROVIDER_virtual/kernel = "different_kernel" right inside in the new image recipe does not have any effect, as that variable seems to be evaluated exclusively in the local.conf machine file, which is read by all recipes.
I'm confident that it is somehow possible in yocto to create an additional image recipe that only differs in kernel, but I'm missing the HOWTO for this seemingly trivial task. :-(
Any hints/links?
With kind regards
-Klaus
Quoted 10 lines · Klaus Knopper
Hello list,
I'm trying to build variantions/brands of an image that only differ in kernel configuration and kernel modules included, but everything else stays the same, for the exact same board, as in the main image.
Setting PREFERRED_PROVIDER_virtual/kernel = "
different_kernel" right inside in the new image recipe does not have any effect, as that variable seems to be evaluated exclusively in the local.conf machine file, which is read by all recipes.
This variable is commonly used inside configuration metadata (machine or distro conf files). You may try it there.
Quoted 10 lines
I'm confident that it is somehow possible in yocto to create an additional image recipe that only differs in kernel, but I'm missing the HOWTO for this seemingly trivial task. :-(
Any hints/links?
With kind regards
-Klaus
Hello Leonardo,
Quoted 7 lines · Leonardo Sandoval
Quoted 6 lines · Klaus Knopper
Hello list,
I'm trying to build variantions/brands of an image that only differ in kernel configuration and kernel modules included, but everything else stays the same, for the exact same board, as in the main image.
Quoted 7 lines
Quoted 4 lines
Setting PREFERRED_PROVIDER_virtual/kernel = "
different_kernel" right inside in the new image recipe does not have any effect, as that variable seems to be evaluated exclusively in the local.conf machine file, which is read by all recipes.This variable is commonly used inside configuration metadata (machine or distro conf files). You may try it there.
Please help me to understand your answer: You are saying that I do have to change the machine or distro config used for ALL recipes, to be able to use a different kernel configuration in ONE recipe, right?
I was really trying to avoid that. :-(
So it is really not possible to just select a different kernel config within a normal recipe without changing the global configuration?
Regards
-Klaus
Quoted 18 lines · Klaus Knopper
Hello Leonardo,
Quoted 7 lines · Leonardo Sandoval
Quoted 6 lines · Klaus Knopper
Hello list,
I'm trying to build variantions/brands of an image that only differ in kernel configuration and kernel modules included, but everything else stays the same, for the exact same board, as in the main image.
Quoted 7 lines
Quoted 4 lines
Setting PREFERRED_PROVIDER_virtual/kernel = "
different_kernel" right inside in the new image recipe does not have any effect, as that variable seems to be evaluated exclusively in the local.conf machine file, which is read by all recipes.This variable is commonly used inside configuration metadata (machine or distro conf files). You may try it there.
Quoted 8 lines
Please help me to understand your answer: You are saying that I do have to change the machine or distro config used for ALL recipes, to be able to use a different kernel configuration in ONE recipe, right?
I was really trying to avoid that. :-(
So it is really not possible to just select a different kernel config within a normal recipe without changing the global configuration?
You really want a different kernel recipe to provide that different kernel configuration. Which looks to be what you are describing, and you just want to switch the provider (again, what you are saying).
Changing the included kernel via that different kernel recipe/package name, and setting it via the preferred provider is the same as any bitbake variable.
So you should be able to set it in any .conf file, and then have what you want. I've used layers with layer.conf files, and similar mechanisms to do what you are trying in the past .. but the longer serving oe/bitbake folks may have a better example to point at.
Cheers,
Bruce
Quoted 4 lines
Regards
-Klaus
Hello Bruce & list,
I need to come back to the topic after quite some failed attempts to solve the problem of switching kernel configurations specific to an image recipe.
Quoted 23 lines · Bruce Ashfield
Quoted 22 lines · Klaus Knopper
Hello Leonardo,
Quoted 7 lines · Leonardo Sandoval
Quoted 6 lines · Klaus Knopper
Hello list,
I'm trying to build variantions/brands of an image that only differ in kernel configuration and kernel modules included, but everything else stays the same, for the exact same board, as in the main image.
Quoted 7 lines
Quoted 4 lines
Setting PREFERRED_PROVIDER_virtual/kernel = "
different_kernel" right inside in the new image recipe does not have any effect, as that variable seems to be evaluated exclusively in the local.conf machine file, which is read by all recipes.This variable is commonly used inside configuration metadata (machine or distro conf files). You may try it there.
Please help me to understand your answer: You are saying that I do have to change the machine or distro config used for ALL recipes, to be able to use a different kernel configuration in ONE recipe, right?
Quoted 8 lines
Quoted 4 lines
I was really trying to avoid that. :-(
So it is really not possible to just select a different kernel config within a normal recipe without changing the global configuration?
You really want a different kernel recipe to provide that different kernel configuration. Which looks to be what you are describing, and you just want to switch the provider (again, what you are saying).
Yes, and I had indeed already added a new kernel recipe, which builds the desired kernel as uImage when calling "bitbake kernel-recipename" directly, but it's ignored by the image recipes. All of them use only the kernel that's defined in build/conf/local.conf as PREFERRED_PROVIDER_virtual/kernel . Redefining the variable in the image recipes has no effect.
Quoted 3 lines
Changing the included kernel via that different kernel recipe/package name, and setting it via the preferred provider is the same as any bitbake variable.
I thought so, but apparently I'mmissing something. It looks like PREFERRED_PROVIDER_virtual/kernel only works in local.conf, i.e. I need to fork the project or change the local.conf file each time I want to use a different kernel. Is this a known or desired behavior?
Quoted 2 lines
So you should be able to set it in any .conf file, and then have what you want.
So, can you confirm that it is not possible to set PREFERRED_PROVIDER_virtual/kernel inside an image recipe?
Quoted 3 lines
I've used layers with layer.conf files, and similar mechanisms to do what you are trying in the past .. but the longer serving oe/bitbake folks may have a better example to point at.
If there are examples for a more convenient way to switch kernels in a recipe rather than inside a .conf file, please point me to the right direction.
Regards
-Klaus
Hi Klaus,
Quoted 2 lines · Klaus Knopper
So, can you confirm that it is not possible to set PREFERRED_PROVIDER_virtual/kernel inside an image recipe?
Confirmed, this is not possible.
I too thought it would make sense to choose one's kernel based on which image you want to build. I was trying this a couple weeks ago and ran into the exact same issue.
The way it was explained to me is as follows: your choice of kernel affects a great many other "downstream" choices, therefore it needs to be known early in the process of bitbake parsing your metadata. As a result, there are only a few, select places where you can select your kernel. Some of these include conf/local.conf, your distro.conf, and your <machine>.conf. Unfortunately your <image>.conf is not one of them.
Also, if your distro or machine set the preferred kernel with an equals sign, it is harder to override in your local.conf. In this case you would need to try appending "_forcevariable" to your choice.
Best regards,
Trevor
There are several solutions:
- Pick one kernel as the "master" one. Create recipes for alternative kernels as required, but blank the (R)PROVIDES so that they do not "provide" a kernel and bitbake will treat them as yet another package to build. In the scripts that you use to deploy the images, pick the kernel that you want.
- Create a new MACHINE for each alternative.
- Set up multiple build environments, share the sstate-cache and similar directories. Each environment can then pick its own kernel etc.
Quoted 65 lines · Klaus Knopper
Hello Bruce & list,
I need to come back to the topic after quite some failed attempts to solve the problem of switching kernel configurations specific to an image recipe.
Quoted 23 lines · Bruce Ashfield
Quoted 22 lines · Klaus Knopper
Hello Leonardo,
Quoted 7 lines · Leonardo Sandoval
Quoted 6 lines · Klaus Knopper
Hello list,
I'm trying to build variantions/brands of an image that only differ in kernel configuration and kernel modules included, but everything else stays the same, for the exact same board, as in the main image.
Quoted 7 lines
Quoted 4 lines
Setting PREFERRED_PROVIDER_virtual/kernel = "
different_kernel" right inside in the new image recipe does not have any effect, as that variable seems to be evaluated exclusively in the local.conf machine file, which is read by all recipes.This variable is commonly used inside configuration metadata (machine or distro conf files). You may try it there.
Please help me to understand your answer: You are saying that I do have to change the machine or distro config used for ALL recipes, to be able to use a different kernel configuration in ONE recipe, right?
Quoted 8 lines
Quoted 4 lines
I was really trying to avoid that. :-(
So it is really not possible to just select a different kernel config within a normal recipe without changing the global configuration?
You really want a different kernel recipe to provide that different kernel configuration. Which looks to be what you are describing, and you just want to switch the provider (again, what you are saying).
Yes, and I had indeed already added a new kernel recipe, which builds the desired kernel as uImage when calling "bitbake kernel-recipename" directly, but it's ignored by the image recipes. All of them use only the kernel that's defined in
build/conf/local.confas PREFERRED_PROVIDER_virtual/kernel . Redefining the variable in the image recipes has no effect.Quoted 3 lines
Changing the included kernel via that different kernel recipe/package name, and setting it via the preferred provider is the same as any bitbake variable.
I thought so, but apparently I'mmissing something. It looks like PREFERRED_PROVIDER_virtual/kernel only works in local.conf, i.e. I need to fork the project or change the local.conf file each time I want to use a different kernel. Is this a known or desired behavior?
Quoted 2 lines
So you should be able to set it in any .conf file, and then have what you want.
So, can you confirm that it is not possible to set PREFERRED_PROVIDER_virtual/kernel inside an image recipe?
Quoted 3 lines
I've used layers with layer.conf files, and similar mechanisms to do what you are trying in the past .. but the longer serving oe/bitbake folks may have a better example to point at.
Quoted 7 lines
If there are examples for a more convenient way to switch kernels in a recipe rather than inside a .conf file, please point me to the right direction.
Regards
-Klaus
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products Eindhovenseweg 32-C, NL-5683 KH Best Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: [email protected]
Website: www.topicproducts.com
Please consider the environment before printing this e-mail