On 06/12/2012 09:06 AM, Dave Billin wrote:
I have an application that utilizes Gumstix OVERO modules on two custom carrier PCB's.  Differences in the hardware on the two carrier PCB's necessitates slightly different kernel recipes for the two processor modules.  To this end, I have created two bitbake recipes that implement the kernel differences and two corresponding image recipes for the processor modules.  I can then switch between the two kernel recipes by setting the value of the "PREFERRED_PROVIDER_virtual/kernel" variable in org.openembedded.dev/conf/machine/overo.c (conveniently accomplished by switching between two git branches).

While my current method works, I'm wondering if someone can recommend a better way to accomplish what I'm doing; specifically one that explicitly ties an image recipe to its corresponding custom kernel recipe.  I've tried overriding PREFERRED_PROVIDER_virtual/kernel in the image recipes, but it results in a parsing error.  From what I've gathered in reading through the OpenEmbedded user's manual, it seems like the kernel recipe gets assigned within the OpenEmbedded machine configuration and nowhere else.

Perhaps this question would be better posed to the OpenEmbedded mailing list, but I thought I would post it here in case one of the experienced Gumstix developers has addressed a similar situation.  Thanks in advance for any helpful comments!

Best Regards,

Dave Billin

Graduate Research Assistant --MS Computer Engineering
University of Idaho
Moscow, Idaho 83844

e-mail: david.billin@vandals.uidaho.edu

Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

gumstix-users mailing list
Not in front of my build machine.
But I believe it is conf/distro where you can find the specific versions.

You can also set preferred providers in your local.conf.
Hope that helps in some way.