linux-yocto defaulting to 3.4.52 for new qemuarmhf.conf

linux-yocto defaulting to 3.4.52 for new qemuarmhf.conf

[Elvis Dowson]

Hi,
      I created a new qemuarmhf.conf, to build using armv7a vfp and neon. 

In the linux-yocto_3.8.bb recipe, I explicitly specified SRCREV_machine_qemuarmhf and added qemuarmhf to the list of COMPATIBLE_MACHINES.

For some reason, it still refuses to build using kernel 3.8, and keeps defaulting to 3.4.52.

I know I can over-ride it in my local.conf by setting a PREFERRED_VERSION_virtual/linux ="3.8" , but I'd like to know what I've missed, to get it to work by default, without setting the over-ride in my local.conf.

Thanks!

Best regards,

Elvis Dowson

Re: linux-yocto defaulting to 3.4.52 for new qemuarmhf.conf

[Elvis Dowson]

On Aug 24, 2013, at 10:00 PM, Elvis Dowson <elvis.dowson@gmail.com> wrote:

> I created a new qemuarmhf.conf, to build using armv7a vfp and neon. 
> 
> In the linux-yocto_3.8.bb recipe, I explicitly specified SRCREV_machine_qemuarmhf and added qemuarmhf to the list of COMPATIBLE_MACHINES.
> 
> For some reason, it still refuses to build using kernel 3.8, and keeps defaulting to 3.4.52.
> 
> I know I can over-ride it in my local.conf by setting a PREFERRED_VERSION_virtual/linux ="3.8" , but I'd like to know what I've missed, to get it to work by default, without setting the over-ride in my local.conf.

Weird, even after setting PREFERRED_VERSION_virtual/linux ="3.8", it still picks up linux-yocto_3.4.bb recipe!

What am I failing to set or configure additionally to get it to work, as intended?

Best regards,

Elvis Dowson

Re: linux-yocto defaulting to 3.4.52 for new qemuarmhf.conf

[Bruce Ashfield]

On Sat, Aug 24, 2013 at 2:06 PM, Elvis Dowson <elvis.dowson@gmail.com> wrote:
>
> On Aug 24, 2013, at 10:00 PM, Elvis Dowson <elvis.dowson@gmail.com> wrote:
>
>> I created a new qemuarmhf.conf, to build using armv7a vfp and neon.
>>
>> In the linux-yocto_3.8.bb recipe, I explicitly specified SRCREV_machine_qemuarmhf and added qemuarmhf to the list of COMPATIBLE_MACHINES.
>>
>> For some reason, it still refuses to build using kernel 3.8, and keeps defaulting to 3.4.52.
>>
>> I know I can over-ride it in my local.conf by setting a PREFERRED_VERSION_virtual/linux ="3.8" , but I'd like to know what I've missed, to get it to work by default, without setting the over-ride in my local.conf.
>
> Weird, even after setting PREFERRED_VERSION_virtual/linux ="3.8", it still picks up linux-yocto_3.4.bb recipe!
>

Try 3.8%, you need to match on the version completely, and it is 3.8...., not
just 3.8.

Bruce

> What am I failing to set or configure additionally to get it to work, as intended?
>
> Best regards,
>
> Elvis Dowson
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: linux-yocto defaulting to 3.4.52 for new qemuarmhf.conf

[Elvis Dowson]

Hi Bruce,

On Aug 25, 2013, at 4:57 AM, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:

>>> I created a new qemuarmhf.conf, to build using armv7a vfp and neon.
>>> 
>>> In the linux-yocto_3.8.bb recipe, I explicitly specified SRCREV_machine_qemuarmhf and added qemuarmhf to the list of COMPATIBLE_MACHINES.
>>> 
>>> For some reason, it still refuses to build using kernel 3.8, and keeps defaulting to 3.4.52.
>>> 
>>> I know I can over-ride it in my local.conf by setting a PREFERRED_VERSION_virtual/linux ="3.8" , but I'd like to know what I've missed, to get it to work by default, without setting the over-ride in my local.conf.
>> 
>> Weird, even after setting PREFERRED_VERSION_virtual/linux ="3.8", it still picks up linux-yocto_3.4.bb recipe!
>> 
> 
> Try 3.8%, you need to match on the version completely, and it is 3.8...., not
> just 3.8.

Ok, I forgot about that! 

Another quick question, why is it that when I create a new qemuarmhf.conf machine configuration, it doesn't automatically pick up the latest linux-yocto_3.8.bb recipe? Why does it attempt to use the 3.4 recipe?

Best regards,

Elvis Dowson

Re: linux-yocto defaulting to 3.4.52 for new qemuarmhf.conf

[Bruce Ashfield]

On 13-08-24 11:32 PM, Elvis Dowson wrote:
> Hi Bruce,
>
> On Aug 25, 2013, at 4:57 AM, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
>
>>>> I created a new qemuarmhf.conf, to build using armv7a vfp and neon.
>>>>
>>>> In the linux-yocto_3.8.bb recipe, I explicitly specified SRCREV_machine_qemuarmhf and added qemuarmhf to the list of COMPATIBLE_MACHINES.
>>>>
>>>> For some reason, it still refuses to build using kernel 3.8, and keeps defaulting to 3.4.52.
>>>>
>>>> I know I can over-ride it in my local.conf by setting a PREFERRED_VERSION_virtual/linux ="3.8" , but I'd like to know what I've missed, to get it to work by default, without setting the over-ride in my local.conf.
>>>
>>> Weird, even after setting PREFERRED_VERSION_virtual/linux ="3.8", it still picks up linux-yocto_3.4.bb recipe!
>>>
>>
>> Try 3.8%, you need to match on the version completely, and it is 3.8...., not
>> just 3.8.
>
> Ok, I forgot about that!
>
> Another quick question, why is it that when I create a new qemuarmhf.conf machine configuration, it doesn't automatically pick up the latest linux-yocto_3.8.bb recipe? Why does it attempt to use the 3.4 recipe?
>

Are you working off master ?

Since you set the compatibility, it should have been picked. But something
else must be changed in your layers, since if you didn't add
3.4 compatibility via bbappends, it never would have been selected
at all.

Cheers,

Bruce

> Best regards,
>
> Elvis Dowson
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

Re: linux-yocto defaulting to 3.4.52 for new qemuarmhf.conf

[Elvis Dowson]

[-- Attachment #1: Type: text/plain, Size: 2317 bytes --]

Hi Bruce,

On Aug 25, 2013, at 9:22 AM, Bruce Ashfield <bruce.ashfield@windriver.com> wrote:

>> Another quick question, why is it that when I create a new qemuarmhf.conf machine configuration, it doesn't automatically pick up the latest linux-yocto_3.8.bb recipe? Why does it attempt to use the 3.4 recipe?
> 
> Are you working off master ?
> 
> Since you set the compatibility, it should have been picked. But something
> else must be changed in your layers, since if you didn't add
> 3.4 compatibility via bbappends, it never would have been selected
> at all.


Yes, I'm currently working off master. If I add the following qemuarmhf.conf file, and apply the patch to linux-yocto_3.8.bb, it still tries to compile linux-yocto_3.4.bb recipe. You should be able to reproduce this fairly easily at your end, with the current poky master. I'm not using any additional layers, just the core yocto default layers.

Filename: qemuarmhf.conf

#@TYPE: Machine
#@NAME: qemuarmhf
#@DESCRIPTION: Machine configuration for QEMU ARM Cortex A9 hard float.

require conf/machine/include/qemu.inc
require conf/machine/include/tune-cortexa9.inc

KERNEL_IMAGETYPE = "zImage"

SERIAL_CONSOLE = "115200 ttyAMA0"


Patch for linux-yocto_3.8.bb

diff --git a/meta/recipes-kernel/linux/linux-yocto_3.8.bb b/meta/recipes-kernel/linux/linux-yocto_3.8.bb
index 790e3e3..787affe 100644
--- a/meta/recipes-kernel/linux/linux-yocto_3.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_3.8.bb
@@ -4,6 +4,7 @@ KBRANCH_DEFAULT = "standard/base"
 KBRANCH = "${KBRANCH_DEFAULT}"
 
 SRCREV_machine_qemuarm ?= "aa76cc28408376814752bd36fb0dcf0e25aa5ba3"
+SRCREV_machine_qemuarmhf ?= "aa76cc28408376814752bd36fb0dcf0e25aa5ba3"
 SRCREV_machine_qemumips  ?= "aa0affda03c955678b26b2fb586f1d9505127871"
 SRCREV_machine_qemumips64 ?= "077bff22c9951db6b35470ba17b1df2f2a91fefb"
 SRCREV_machine_qemuppc ?= "698eada61d9385b42dd117858b943655b565084b"
@@ -21,7 +22,7 @@ PV = "${LINUX_VERSION}+git${SRCPV}"
 
 KMETA = "meta"
 
-COMPATIBLE_MACHINE = "qemuarm|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
+COMPATIBLE_MACHINE = "qemuarm|qemuarmhf|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
 
 # Functionality flags
 KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"

Best regards,

Elvis Dowson

[-- Attachment #2: Type: text/html, Size: 3036 bytes --]

Re: linux-yocto defaulting to 3.4.52 for new qemuarmhf.conf

[Bruce Ashfield]

On 13-08-25 10:25 AM, Elvis Dowson wrote:
> Hi Bruce,
>
> On Aug 25, 2013, at 9:22 AM, Bruce Ashfield
> <bruce.ashfield@windriver.com <mailto:bruce.ashfield@windriver.com>> wrote:
>
>>> Another quick question, why is it that when I create a new
>>> qemuarmhf.conf machine configuration, it doesn't automatically pick
>>> up the latest linux-yocto_3.8.bb recipe? Why does it attempt to use
>>> the 3.4 recipe?
>>
>> Are you working off master ?
>>
>> Since you set the compatibility, it should have been picked. But something
>> else must be changed in your layers, since if you didn't add
>> 3.4 compatibility via bbappends, it never would have been selected
>> at all.
>
> Yes, I'm currently working off master. If I add the following
> qemuarmhf.conf file, and apply the patch to linux-yocto_3.8.bb, it still
> tries to compile linux-yocto_3.4.bb recipe. You should be able to
> reproduce this fairly easily at your end, with the current poky master.
> I'm not using any additional layers, just the core yocto default layers.

If you are using yocto and poky as the reference distro:

./conf/distro/poky.conf:PREFERRED_VERSION_linux-yocto ?= "3.4%"

Is where you are getting the default to 3.4.

I plan to bump that once we've shaken all the issues out of 3.10.

Cheers,

Bruce

>
> *_Filename: qemuarmhf.conf_*
>
> #@TYPE: Machine
> #@NAME: qemuarmhf
> #@DESCRIPTION: Machine configuration for QEMU ARM Cortex A9 hard float.
>
> require conf/machine/include/qemu.inc
> require conf/machine/include/tune-cortexa9.inc
>
> KERNEL_IMAGETYPE = "zImage"
>
> SERIAL_CONSOLE = "115200 ttyAMA0"
>
>
> *_Patch for linux-yocto_3.8.bb_*
>
> diff --git a/meta/recipes-kernel/linux/linux-yocto_3.8.bb
> b/meta/recipes-kernel/linux/linux-yocto_3.8.bb
> index 790e3e3..787affe 100644
> --- a/meta/recipes-kernel/linux/linux-yocto_3.8.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto_3.8.bb
> @@ -4,6 +4,7 @@ KBRANCH_DEFAULT = "standard/base"
>   KBRANCH = "${KBRANCH_DEFAULT}"
>
>   SRCREV_machine_qemuarm ?= "aa76cc28408376814752bd36fb0dcf0e25aa5ba3"
> +SRCREV_machine_qemuarmhf ?= "aa76cc28408376814752bd36fb0dcf0e25aa5ba3"
>   SRCREV_machine_qemumips  ?= "aa0affda03c955678b26b2fb586f1d9505127871"
>   SRCREV_machine_qemumips64 ?= "077bff22c9951db6b35470ba17b1df2f2a91fefb"
>   SRCREV_machine_qemuppc ?= "698eada61d9385b42dd117858b943655b565084b"
> @@ -21,7 +22,7 @@ PV = "${LINUX_VERSION}+git${SRCPV}"
>
>   KMETA = "meta"
>
> -COMPATIBLE_MACHINE =
> "qemuarm|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
> +COMPATIBLE_MACHINE =
> "qemuarm|qemuarmhf|qemux86|qemuppc|qemumips|qemumips64|qemux86-64"
>
>   # Functionality flags
>   KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc"
>
> Best regards,
>
> Elvis Dowson