[oe] How update kernel recipe?

Philip Balister philip at balister.org
Fri Jul 18 11:08:23 UTC 2008


Ulf Samuelsson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I have built "gpe-image" for AT91SAM9263EK
> after fixing libsvg-cairo manually due to the LT_VERSION problem.
> 
> I would like to upgrade the kernel for AT91SAM9263EK.
> I created a recipe for linux-2.6.25.10 called
> "packages/linux/linux-atmel_2.6.25.10.bb" (found below)
> with DEFAULT_PREFERENCE_at91sam9263ek = "30"
> 
> 2.6.25.10 is properly built when I run:
> $ bitbake -b linux-atmel
> 
> When I run
> $ bitbake -b gpe-image
> it still builds "packages/linux/linux_2.6.20.bb"
> with DEFAULT_PREFERENCE_at91sam9263ek = "20"
> 
> The at91sam9263ek.conf file says:
> PREFERRED_PROVIDER_virtual/kernel = "linux"
> 
> I have been trying to figure out how the recipe selection
> process works, and I assume that all bb files starting
> with "linux" will be considered, and then the
> highest DEFAULT_PREFERENCE_<machine> will be used
> to select linux.
> 
> This obviously is not correct, since 2.6.20 is built.
> 
> Do I need to change PREFERRED_PROVIDER_virtual/kernel
> to "linux-atmel"?
> In that case, why?

Yes. The part after the - is not special. When you say PREFERRED_PRVIDER 
= "linux" bitbake will build linux_version, if you put "linux-foo" it 
will build linux-foo_version.

Philip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3303 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20080718/a1e29658/attachment-0002.bin>


More information about the Openembedded-devel mailing list