[oe] How does OE determine the kernel version that gets build?

Lars Holowko Lars.Holowko at lantronix.com
Wed Jul 8 14:36:27 UTC 2009


Thanks Khem,

I'd swear that that line was not in conf/machine/at91sam9g20ek.conf but
that would make me look even siller, wouldn't it? ;-)
You saved me from going crazy...

Everything works fine.

Lars

-----Original Message-----
From: Khem Raj [mailto:raj.khem at gmail.com] 
Sent: Tuesday, July 07, 2009 5:14 PM
To: openembedded-devel at lists.openembedded.org
Cc: Lars Holowko
Subject: Re: [oe] How does OE determine the kernel version that gets
build?

On Tuesday 07 July 2009 03:13:56 pm Lars Holowko wrote:
> Hi everybody,
> 
> I am working with an Atmel AT91SAM9G20-EK evaluation board. I was able

> to successfully build the console-image and the default 2.6.28 kernel 
> for it.
> 
> Now I want to switch to a 2.6.30 kernel (for better wireless support) 
> but bitbake linux or bitbake console-image always builds 2.6.28
instead.
> I copied a defconfig to recipies/linux/linux-2.6.30/at91sam9g20ek,
> copied the AT91 patches for 2.6.30 in its place and added a 
> DEFAULT_PREFERENCE_at91sam9g20ek = "30" line to 
> recipies/linux/linux_2.6.30.bb hoping to make the 2.6.30 kernel
active.
> 
> I can build a running kernel 2.6.30 with bitbake -b 
> recipies/linux/linux_2.6.30.bb.
> 
> Funnily there is no DEFAULT_PREFERENCE_at91sam9g20ek line in 
> recipies/linux/linux_2.6.28.bb and its DEFAULT_PREFERENCE = "-1" so I 
> do not even understand why that kernel gets chosen at all.


because in conf/machine/at91sam9g20ek.conf it says it wants 2.6.28

PREFERRED_VERSION_linux = "2.6.28"

change that and it should pick whatever you chose instead of 2.6.28

Khem
 
**********************************************************************
This e-mail is the property of Lantronix. It is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. Distribution or copying of this e-mail, or the information contained herein, to anyone other than the intended recipient is prohibited.




More information about the Openembedded-devel mailing list