Topics

#av1 #armv6 #raspberrypi #neon #raspberrypi #av1 #neon #armv6


safouane maaloul
 

Hello folks,
 
I have an issue integrating av1  in yocto. I get the  compile  error "compiling simd-neon.h requires -mfpu=neon or equivalent". The problem is that i use armv6 (raspberrypi zero w) so i can't exactly do that. Anyone have a workaround this problem ?

Best regards,

Safouane.Maaloul


Zoran
 

So, what is your MACHINE variable set to?

Maybe knowing that, somebody can help.

Zee


safouane maaloul
 



Le mer. 17 févr. 2021 à 13:18, safouane maaloul <maaloulsafouane@...> a écrit :
Yeah i know the problem is i am using armv6 (raspberry pi zero w) and there isn’t that option so i need a workaround ?

Best regards,

Safouane.Maaloul  

Le mer. 17 févr. 2021 à 13:13, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
> ...compile  error "compiling simd-neon.h requires -mfpu=
> neon or equivalent"...

IIRC, this has to do with the platform chosen.

I know that for armv7 there are two types of machine:
MACHINE ?= "armv7" (FP library in SW)
MACHINE ?= "armv7hf" (hard FP = neon)

I guess you did set up the MACHINE variable with postfix fp, most probably.

My 2 cent worth answer,
Zee
_______


On Wed, Feb 17, 2021 at 11:00 AM safouane maaloul
<maaloulsafouane@...> wrote:
>
> Hello folks,
>
> I have an issue integrating av1  in yocto. I get the  compile  error "compiling simd-neon.h requires -mfpu=neon or equivalent". The problem is that i use armv6 (raspberrypi zero w) so i can't exactly do that. Anyone have a workaround this problem ?
>
> Best regards,
>
> Safouane.Maaloul
>
>
--
SAFOUANE MAALOUL


--
SAFOUANE MAALOUL


safouane maaloul
 



Le jeu. 18 févr. 2021 à 12:44, safouane maaloul <maaloulsafouane@...> a écrit :
This is my build configuration :
Build Configuration:
BB_VERSION           = "1.46.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "arm-poky-linux-gnueabi"
MACHINE              = "raspberrypi0-wifi"
DISTRO               = "poky"
DISTRO_VERSION       = "3.1.5"
TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"
TARGET_FPU           = "hard"
meta
meta-poky
meta-yocto-bsp       = "dunfell:7ea41de13774675828239b7738d3f5d70be8b1af"
meta-oe
meta-multimedia
meta-networking
meta-python          = "dunfell:5bba79488b7d393d2258d6e917f7bf7b0d7c4073"
meta-raspberrypi     = "dunfell:987993209716302eb8f314f69a2a3340555f94d8"
meta-gstreamer1.0    = "dunfell:b489b1ba084544d9c4c08f7c3b3d1c37ffa53c51"

Best regards,

Safouane

Le mer. 17 févr. 2021 à 13:24, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
So, what is your MACHINE variable set to?

Maybe knowing that, somebody can help.

Zee


--
SAFOUANE MAALOUL


--
SAFOUANE MAALOUL


Zoran
 

TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
Here is an interesting reading for you, for me also:
https://www.yoctoproject.org/pipermail/meta-xilinx/2015-July/001060.html

What I am getting from this reading is that you need to try with the
following line:
TUNE_FEATURES = "arm armv6 vfp arm1176jzfs"

I guess, YOCTO people have not too much experience with armv6, nor me,
but this should be (I hope) generic.

Hope this helps.
Zoran
_______

On Thu, Feb 18, 2021 at 12:44 PM safouane maaloul
<maaloulsafouane@gmail.com> wrote:

This is my build configuration :
Build Configuration:
BB_VERSION = "1.46.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "raspberrypi0-wifi"
DISTRO = "poky"
DISTRO_VERSION = "3.1.5"
TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "dunfell:7ea41de13774675828239b7738d3f5d70be8b1af"
meta-oe
meta-multimedia
meta-networking
meta-python = "dunfell:5bba79488b7d393d2258d6e917f7bf7b0d7c4073"
meta-raspberrypi = "dunfell:987993209716302eb8f314f69a2a3340555f94d8"
meta-gstreamer1.0 = "dunfell:b489b1ba084544d9c4c08f7c3b3d1c37ffa53c51"

Best regards,

Safouane

Le mer. 17 févr. 2021 à 13:24, Zoran Stojsavljevic <zoran.stojsavljevic@gmail.com> a écrit :

So, what is your MACHINE variable set to?

Maybe knowing that, somebody can help.

Zee


--
SAFOUANE MAALOUL
maaloulsafouane@gmail.com


safouane maaloul
 

Yes I will check it. Do you know how to remove callconvention-hard from TUNE_FEATURES ?

Best regards,

Safouane

Le jeu. 18 févr. 2021 à 14:52, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
> TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"

Here is an interesting reading for you, for me also:
https://www.yoctoproject.org/pipermail/meta-xilinx/2015-July/001060.html

What I am getting from this reading is that you need to try with the
following line:
TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs"

I guess, YOCTO people have not too much experience with armv6, nor me,
but this should be (I hope) generic.

Hope this helps.
Zoran
_______

On Thu, Feb 18, 2021 at 12:44 PM safouane maaloul
<maaloulsafouane@...> wrote:
>
> This is my build configuration :
> Build Configuration:
> BB_VERSION           = "1.46.0"
> BUILD_SYS            = "x86_64-linux"
> NATIVELSBSTRING      = "universal"
> TARGET_SYS           = "arm-poky-linux-gnueabi"
> MACHINE              = "raspberrypi0-wifi"
> DISTRO               = "poky"
> DISTRO_VERSION       = "3.1.5"
> TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"
> TARGET_FPU           = "hard"
> meta
> meta-poky
> meta-yocto-bsp       = "dunfell:7ea41de13774675828239b7738d3f5d70be8b1af"
> meta-oe
> meta-multimedia
> meta-networking
> meta-python          = "dunfell:5bba79488b7d393d2258d6e917f7bf7b0d7c4073"
> meta-raspberrypi     = "dunfell:987993209716302eb8f314f69a2a3340555f94d8"
> meta-gstreamer1.0    = "dunfell:b489b1ba084544d9c4c08f7c3b3d1c37ffa53c51"
>
> Best regards,
>
> Safouane
>
> Le mer. 17 févr. 2021 à 13:24, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>>
>> So, what is your MACHINE variable set to?
>>
>> Maybe knowing that, somebody can help.
>>
>> Zee
>
>
>
> --
> SAFOUANE MAALOUL
> maaloulsafouane@...
>


--
SAFOUANE MAALOUL


Zoran
 

https://yocto.yoctoproject.narkive.com/Wle40I09/gcc-on-arm

https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-TUNE_FEATURES
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-AVAILTUNES

Zee
_______

On Thu, Feb 18, 2021 at 3:28 PM safouane maaloul
<maaloulsafouane@gmail.com> wrote:

Yes I will check it. Do you know how to remove callconvention-hard from TUNE_FEATURES ?

Best regards,

Safouane

Le jeu. 18 févr. 2021 à 14:52, Zoran Stojsavljevic <zoran.stojsavljevic@gmail.com> a écrit :

TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
Here is an interesting reading for you, for me also:
https://www.yoctoproject.org/pipermail/meta-xilinx/2015-July/001060.html

What I am getting from this reading is that you need to try with the
following line:
TUNE_FEATURES = "arm armv6 vfp arm1176jzfs"

I guess, YOCTO people have not too much experience with armv6, nor me,
but this should be (I hope) generic.

Hope this helps.
Zoran
_______

On Thu, Feb 18, 2021 at 12:44 PM safouane maaloul
<maaloulsafouane@gmail.com> wrote:

This is my build configuration :
Build Configuration:
BB_VERSION = "1.46.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "raspberrypi0-wifi"
DISTRO = "poky"
DISTRO_VERSION = "3.1.5"
TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "dunfell:7ea41de13774675828239b7738d3f5d70be8b1af"
meta-oe
meta-multimedia
meta-networking
meta-python = "dunfell:5bba79488b7d393d2258d6e917f7bf7b0d7c4073"
meta-raspberrypi = "dunfell:987993209716302eb8f314f69a2a3340555f94d8"
meta-gstreamer1.0 = "dunfell:b489b1ba084544d9c4c08f7c3b3d1c37ffa53c51"

Best regards,

Safouane

Le mer. 17 févr. 2021 à 13:24, Zoran Stojsavljevic <zoran.stojsavljevic@gmail.com> a écrit :

So, what is your MACHINE variable set to?

Maybe knowing that, somebody can help.

Zee


--
SAFOUANE MAALOUL
maaloulsafouane@gmail.com


--
SAFOUANE MAALOUL
maaloulsafouane@gmail.com


safouane maaloul
 

I succed in removing callconvention-hard from TUNE_FEATURES ? But i have the same problem. I am pretty sure that i get get it working if i add neon to the TUNE_FEATURES. Something like this     TUNE_FEATURES= "arm armv6 vfp arm1176jzfs callconvention-hard neon". But I can't do it with armv6. I have to use raspberrypi zero w so i have to make it work with armv6. I know that i can make it work with armv7 and armv8. I have error like this : | In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:20:
| /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:528:24: note: called from here
|   528 |   const int16x4_t s1 = vmovn_s32(v1); 
|       |                        ^~~~~~~~~~~~~
| In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:12:
| /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/recipe-sysroot-native/usr/lib/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/10.2.0/include/arm_neon.h:7556:1: error: inlining failed in call to 'always_inline' 'vmovn_s32': target specific option mismatch
|  7556 | vmovn_s32 (int32x4_t __a)
|       | ^~~~~~~~~

So i am sure i have to add the neon feature so i appreciate it if someone can help me. I didn't find a workaround this problem on the internet.

Best regards,

Safouane


Le jeu. 18 févr. 2021 à 18:00, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
https://yocto.yoctoproject.narkive.com/Wle40I09/gcc-on-arm

https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-TUNE_FEATURES
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-AVAILTUNES

Zee
_______

On Thu, Feb 18, 2021 at 3:28 PM safouane maaloul
<maaloulsafouane@...> wrote:
>
> Yes I will check it. Do you know how to remove callconvention-hard from TUNE_FEATURES ?
>
> Best regards,
>
> Safouane
>
> Le jeu. 18 févr. 2021 à 14:52, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>>
>> > TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"
>>
>> Here is an interesting reading for you, for me also:
>> https://www.yoctoproject.org/pipermail/meta-xilinx/2015-July/001060.html
>>
>> What I am getting from this reading is that you need to try with the
>> following line:
>> TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs"
>>
>> I guess, YOCTO people have not too much experience with armv6, nor me,
>> but this should be (I hope) generic.
>>
>> Hope this helps.
>> Zoran
>> _______
>>
>> On Thu, Feb 18, 2021 at 12:44 PM safouane maaloul
>> <maaloulsafouane@...> wrote:
>> >
>> > This is my build configuration :
>> > Build Configuration:
>> > BB_VERSION           = "1.46.0"
>> > BUILD_SYS            = "x86_64-linux"
>> > NATIVELSBSTRING      = "universal"
>> > TARGET_SYS           = "arm-poky-linux-gnueabi"
>> > MACHINE              = "raspberrypi0-wifi"
>> > DISTRO               = "poky"
>> > DISTRO_VERSION       = "3.1.5"
>> > TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"
>> > TARGET_FPU           = "hard"
>> > meta
>> > meta-poky
>> > meta-yocto-bsp       = "dunfell:7ea41de13774675828239b7738d3f5d70be8b1af"
>> > meta-oe
>> > meta-multimedia
>> > meta-networking
>> > meta-python          = "dunfell:5bba79488b7d393d2258d6e917f7bf7b0d7c4073"
>> > meta-raspberrypi     = "dunfell:987993209716302eb8f314f69a2a3340555f94d8"
>> > meta-gstreamer1.0    = "dunfell:b489b1ba084544d9c4c08f7c3b3d1c37ffa53c51"
>> >
>> > Best regards,
>> >
>> > Safouane
>> >
>> > Le mer. 17 févr. 2021 à 13:24, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>> >>
>> >> So, what is your MACHINE variable set to?
>> >>
>> >> Maybe knowing that, somebody can help.
>> >>
>> >> Zee
>> >
>> >
>> >
>> > --
>> > SAFOUANE MAALOUL
>> > maaloulsafouane@...
>> >
>
>
>
> --
> SAFOUANE MAALOUL
> maaloulsafouane@...
>


--
SAFOUANE MAALOUL


Khem Raj
 

can you try adding

EXTRA_OECMAKE += "-DHAVE_NEON=0"

and see if that helps ? for whatever reason set_aom_detect_var is
enabling it where as default should be 0

On Thu, Feb 18, 2021 at 10:42 AM safouane maaloul
<maaloulsafouane@gmail.com> wrote:

I succed in removing callconvention-hard from TUNE_FEATURES ? But i have the same problem. I am pretty sure that i get get it working if i add neon to the TUNE_FEATURES. Something like this TUNE_FEATURES= "arm armv6 vfp arm1176jzfs callconvention-hard neon". But I can't do it with armv6. I have to use raspberrypi zero w so i have to make it work with armv6. I know that i can make it work with armv7 and armv8. I have error like this : | In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:20:
| /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:528:24: note: called from here
| 528 | const int16x4_t s1 = vmovn_s32(v1);
| | ^~~~~~~~~~~~~
| In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:12:
| /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/recipe-sysroot-native/usr/lib/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/10.2.0/include/arm_neon.h:7556:1: error: inlining failed in call to 'always_inline' 'vmovn_s32': target specific option mismatch
| 7556 | vmovn_s32 (int32x4_t __a)
| | ^~~~~~~~~

So i am sure i have to add the neon feature so i appreciate it if someone can help me. I didn't find a workaround this problem on the internet.

Best regards,

Safouane

Le jeu. 18 févr. 2021 à 18:00, Zoran Stojsavljevic <zoran.stojsavljevic@gmail.com> a écrit :

https://yocto.yoctoproject.narkive.com/Wle40I09/gcc-on-arm

https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-TUNE_FEATURES
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-AVAILTUNES

Zee
_______

On Thu, Feb 18, 2021 at 3:28 PM safouane maaloul
<maaloulsafouane@gmail.com> wrote:

Yes I will check it. Do you know how to remove callconvention-hard from TUNE_FEATURES ?

Best regards,

Safouane

Le jeu. 18 févr. 2021 à 14:52, Zoran Stojsavljevic <zoran.stojsavljevic@gmail.com> a écrit :

TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
Here is an interesting reading for you, for me also:
https://www.yoctoproject.org/pipermail/meta-xilinx/2015-July/001060.html

What I am getting from this reading is that you need to try with the
following line:
TUNE_FEATURES = "arm armv6 vfp arm1176jzfs"

I guess, YOCTO people have not too much experience with armv6, nor me,
but this should be (I hope) generic.

Hope this helps.
Zoran
_______

On Thu, Feb 18, 2021 at 12:44 PM safouane maaloul
<maaloulsafouane@gmail.com> wrote:

This is my build configuration :
Build Configuration:
BB_VERSION = "1.46.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "raspberrypi0-wifi"
DISTRO = "poky"
DISTRO_VERSION = "3.1.5"
TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "dunfell:7ea41de13774675828239b7738d3f5d70be8b1af"
meta-oe
meta-multimedia
meta-networking
meta-python = "dunfell:5bba79488b7d393d2258d6e917f7bf7b0d7c4073"
meta-raspberrypi = "dunfell:987993209716302eb8f314f69a2a3340555f94d8"
meta-gstreamer1.0 = "dunfell:b489b1ba084544d9c4c08f7c3b3d1c37ffa53c51"

Best regards,

Safouane

Le mer. 17 févr. 2021 à 13:24, Zoran Stojsavljevic <zoran.stojsavljevic@gmail.com> a écrit :

So, what is your MACHINE variable set to?

Maybe knowing that, somebody can help.

Zee


--
SAFOUANE MAALOUL
maaloulsafouane@gmail.com


--
SAFOUANE MAALOUL
maaloulsafouane@gmail.com


--
SAFOUANE MAALOUL
maaloulsafouane@gmail.com




safouane maaloul
 

I have an erreur:
| /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:525:24: note: called from here
|   525 |   const int32x4_t v0 = vld1q_s32(buf);
|       |                        ^~~~~~~~~~~~~~
| ninja: build stopped: subcommand failed.
| WARNING: /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037:155 exit 1 from 'eval ${DESTDIR:+DESTDIR=${DESTDIR} }VERBOSE=1 cmake --build '/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/build' "$@" -- ${EXTRA_OECMAKE_BUILD}'
| WARNING: Backtrace (BB generated script):
|       #1: cmake_runcmake_build, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 155
|       #2: cmake_do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 149
|       #3: do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 144
|       #4: main, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 168
|
| Backtrace (metadata-relative locations):
|       #1: cmake_runcmake_build, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../poky/meta/classes/cmake.bbclass, line 205
|       #2: cmake_do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../poky/meta/classes/cmake.bbclass, line 209
|       #3: do_compile, autogenerated, line 2
ERROR: Task (/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../meta-openembedded/meta-multimedia/recipes-multimedia/aom/aom_2.0.0.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3538 tasks of which 3326 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../meta-openembedded/meta-multimedia/recipes-multimedia/aom/aom_2.0.0.bb:do_compile
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Do you have any idea why it didn't work ?

Best regards,

Safouane


Le jeu. 18 févr. 2021 à 20:54, Khem Raj <raj.khem@...> a écrit :
can you try adding

EXTRA_OECMAKE += "-DHAVE_NEON=0"

and see if that helps ? for whatever reason set_aom_detect_var is
enabling it where as default should be 0

On Thu, Feb 18, 2021 at 10:42 AM safouane maaloul
<maaloulsafouane@...> wrote:
>
> I succed in removing callconvention-hard from TUNE_FEATURES ? But i have the same problem. I am pretty sure that i get get it working if i add neon to the TUNE_FEATURES. Something like this     TUNE_FEATURES= "arm armv6 vfp arm1176jzfs callconvention-hard neon". But I can't do it with armv6. I have to use raspberrypi zero w so i have to make it work with armv6. I know that i can make it work with armv7 and armv8. I have error like this : | In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:20:
> | /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:528:24: note: called from here
> |   528 |   const int16x4_t s1 = vmovn_s32(v1);
> |       |                        ^~~~~~~~~~~~~
> | In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:12:
> | /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/recipe-sysroot-native/usr/lib/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/10.2.0/include/arm_neon.h:7556:1: error: inlining failed in call to 'always_inline' 'vmovn_s32': target specific option mismatch
> |  7556 | vmovn_s32 (int32x4_t __a)
> |       | ^~~~~~~~~
>
> So i am sure i have to add the neon feature so i appreciate it if someone can help me. I didn't find a workaround this problem on the internet.
>
> Best regards,
>
> Safouane
>
> Le jeu. 18 févr. 2021 à 18:00, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>>
>> https://yocto.yoctoproject.narkive.com/Wle40I09/gcc-on-arm
>>
>> https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-TUNE_FEATURES
>> https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-AVAILTUNES
>>
>> Zee
>> _______
>>
>> On Thu, Feb 18, 2021 at 3:28 PM safouane maaloul
>> <maaloulsafouane@...> wrote:
>> >
>> > Yes I will check it. Do you know how to remove callconvention-hard from TUNE_FEATURES ?
>> >
>> > Best regards,
>> >
>> > Safouane
>> >
>> > Le jeu. 18 févr. 2021 à 14:52, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>> >>
>> >> > TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"
>> >>
>> >> Here is an interesting reading for you, for me also:
>> >> https://www.yoctoproject.org/pipermail/meta-xilinx/2015-July/001060.html
>> >>
>> >> What I am getting from this reading is that you need to try with the
>> >> following line:
>> >> TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs"
>> >>
>> >> I guess, YOCTO people have not too much experience with armv6, nor me,
>> >> but this should be (I hope) generic.
>> >>
>> >> Hope this helps.
>> >> Zoran
>> >> _______
>> >>
>> >> On Thu, Feb 18, 2021 at 12:44 PM safouane maaloul
>> >> <maaloulsafouane@...> wrote:
>> >> >
>> >> > This is my build configuration :
>> >> > Build Configuration:
>> >> > BB_VERSION           = "1.46.0"
>> >> > BUILD_SYS            = "x86_64-linux"
>> >> > NATIVELSBSTRING      = "universal"
>> >> > TARGET_SYS           = "arm-poky-linux-gnueabi"
>> >> > MACHINE              = "raspberrypi0-wifi"
>> >> > DISTRO               = "poky"
>> >> > DISTRO_VERSION       = "3.1.5"
>> >> > TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"
>> >> > TARGET_FPU           = "hard"
>> >> > meta
>> >> > meta-poky
>> >> > meta-yocto-bsp       = "dunfell:7ea41de13774675828239b7738d3f5d70be8b1af"
>> >> > meta-oe
>> >> > meta-multimedia
>> >> > meta-networking
>> >> > meta-python          = "dunfell:5bba79488b7d393d2258d6e917f7bf7b0d7c4073"
>> >> > meta-raspberrypi     = "dunfell:987993209716302eb8f314f69a2a3340555f94d8"
>> >> > meta-gstreamer1.0    = "dunfell:b489b1ba084544d9c4c08f7c3b3d1c37ffa53c51"
>> >> >
>> >> > Best regards,
>> >> >
>> >> > Safouane
>> >> >
>> >> > Le mer. 17 févr. 2021 à 13:24, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>> >> >>
>> >> >> So, what is your MACHINE variable set to?
>> >> >>
>> >> >> Maybe knowing that, somebody can help.
>> >> >>
>> >> >> Zee
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > SAFOUANE MAALOUL
>> >> > maaloulsafouane@...
>> >> >
>> >
>> >
>> >
>> > --
>> > SAFOUANE MAALOUL
>> > maaloulsafouane@...
>> >
>
>
>
> --
> SAFOUANE MAALOUL
> maaloulsafouane@...
>
>
>
>


--
SAFOUANE MAALOUL


Khem Raj
 

Well we do not enable neon for this tune but aom still seems to want it so I would suggest to look at the build and see if it’s disabling neon and have HAVE_NEON is not set properly 

On Thu, Feb 18, 2021 at 12:12 PM safouane maaloul <maaloulsafouane@...> wrote:
I have an erreur:
| /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:525:24: note: called from here
|   525 |   const int32x4_t v0 = vld1q_s32(buf);
|       |                        ^~~~~~~~~~~~~~
| ninja: build stopped: subcommand failed.
| WARNING: /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037:155 exit 1 from 'eval ${DESTDIR:+DESTDIR=${DESTDIR} }VERBOSE=1 cmake --build '/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/build' "$@" -- ${EXTRA_OECMAKE_BUILD}'
| WARNING: Backtrace (BB generated script):
|       #1: cmake_runcmake_build, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 155
|       #2: cmake_do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 149
|       #3: do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 144
|       #4: main, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 168
|
| Backtrace (metadata-relative locations):
|       #1: cmake_runcmake_build, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../poky/meta/classes/cmake.bbclass, line 205
|       #2: cmake_do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../poky/meta/classes/cmake.bbclass, line 209
|       #3: do_compile, autogenerated, line 2
ERROR: Task (/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../meta-openembedded/meta-multimedia/recipes-multimedia/aom/aom_2.0.0.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3538 tasks of which 3326 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../meta-openembedded/meta-multimedia/recipes-multimedia/aom/aom_2.0.0.bb:do_compile
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Do you have any idea why it didn't work ?

Best regards,

Safouane

Le jeu. 18 févr. 2021 à 20:54, Khem Raj <raj.khem@...> a écrit :
can you try adding

EXTRA_OECMAKE += "-DHAVE_NEON=0"

and see if that helps ? for whatever reason set_aom_detect_var is
enabling it where as default should be 0

On Thu, Feb 18, 2021 at 10:42 AM safouane maaloul
<maaloulsafouane@...> wrote:
>
> I succed in removing callconvention-hard from TUNE_FEATURES ? But i have the same problem. I am pretty sure that i get get it working if i add neon to the TUNE_FEATURES. Something like this     TUNE_FEATURES= "arm armv6 vfp arm1176jzfs callconvention-hard neon". But I can't do it with armv6. I have to use raspberrypi zero w so i have to make it work with armv6. I know that i can make it work with armv7 and armv8. I have error like this : | In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:20:
> | /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:528:24: note: called from here
> |   528 |   const int16x4_t s1 = vmovn_s32(v1);
> |       |                        ^~~~~~~~~~~~~
> | In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:12:
> | /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/recipe-sysroot-native/usr/lib/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/10.2.0/include/arm_neon.h:7556:1: error: inlining failed in call to 'always_inline' 'vmovn_s32': target specific option mismatch
> |  7556 | vmovn_s32 (int32x4_t __a)
> |       | ^~~~~~~~~
>
> So i am sure i have to add the neon feature so i appreciate it if someone can help me. I didn't find a workaround this problem on the internet.
>
> Best regards,
>
> Safouane
>
> Le jeu. 18 févr. 2021 à 18:00, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>>
>> https://yocto.yoctoproject.narkive.com/Wle40I09/gcc-on-arm
>>
>> https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-TUNE_FEATURES
>> https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-AVAILTUNES
>>
>> Zee
>> _______
>>
>> On Thu, Feb 18, 2021 at 3:28 PM safouane maaloul
>> <maaloulsafouane@...> wrote:
>> >
>> > Yes I will check it. Do you know how to remove callconvention-hard from TUNE_FEATURES ?
>> >
>> > Best regards,
>> >
>> > Safouane
>> >
>> > Le jeu. 18 févr. 2021 à 14:52, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>> >>
>> >> > TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"
>> >>
>> >> Here is an interesting reading for you, for me also:
>> >> https://www.yoctoproject.org/pipermail/meta-xilinx/2015-July/001060.html
>> >>
>> >> What I am getting from this reading is that you need to try with the
>> >> following line:
>> >> TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs"
>> >>
>> >> I guess, YOCTO people have not too much experience with armv6, nor me,
>> >> but this should be (I hope) generic.
>> >>
>> >> Hope this helps.
>> >> Zoran
>> >> _______
>> >>
>> >> On Thu, Feb 18, 2021 at 12:44 PM safouane maaloul
>> >> <maaloulsafouane@...> wrote:
>> >> >
>> >> > This is my build configuration :
>> >> > Build Configuration:
>> >> > BB_VERSION           = "1.46.0"
>> >> > BUILD_SYS            = "x86_64-linux"
>> >> > NATIVELSBSTRING      = "universal"
>> >> > TARGET_SYS           = "arm-poky-linux-gnueabi"
>> >> > MACHINE              = "raspberrypi0-wifi"
>> >> > DISTRO               = "poky"
>> >> > DISTRO_VERSION       = "3.1.5"
>> >> > TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"
>> >> > TARGET_FPU           = "hard"
>> >> > meta
>> >> > meta-poky
>> >> > meta-yocto-bsp       = "dunfell:7ea41de13774675828239b7738d3f5d70be8b1af"
>> >> > meta-oe
>> >> > meta-multimedia
>> >> > meta-networking
>> >> > meta-python          = "dunfell:5bba79488b7d393d2258d6e917f7bf7b0d7c4073"
>> >> > meta-raspberrypi     = "dunfell:987993209716302eb8f314f69a2a3340555f94d8"
>> >> > meta-gstreamer1.0    = "dunfell:b489b1ba084544d9c4c08f7c3b3d1c37ffa53c51"
>> >> >
>> >> > Best regards,
>> >> >
>> >> > Safouane
>> >> >
>> >> > Le mer. 17 févr. 2021 à 13:24, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>> >> >>
>> >> >> So, what is your MACHINE variable set to?
>> >> >>
>> >> >> Maybe knowing that, somebody can help.
>> >> >>
>> >> >> Zee
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > SAFOUANE MAALOUL
>> >> > maaloulsafouane@...
>> >> >
>> >
>> >
>> >
>> > --
>> > SAFOUANE MAALOUL
>> > maaloulsafouane@...
>> >
>
>
>
> --
> SAFOUANE MAALOUL
> maaloulsafouane@...
>
>
>
>


--
SAFOUANE MAALOUL


safouane maaloul
 

Sorry to annoying you with my question but how do i find where HAVE_NEON is set ? 

Best regards,

Safouane 

Le jeu. 18 févr. 2021 à 21:16, Khem Raj <raj.khem@...> a écrit :
Well we do not enable neon for this tune but aom still seems to want it so I would suggest to look at the build and see if it’s disabling neon and have HAVE_NEON is not set properly 

On Thu, Feb 18, 2021 at 12:12 PM safouane maaloul <maaloulsafouane@...> wrote:
I have an erreur:
| /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:525:24: note: called from here
|   525 |   const int32x4_t v0 = vld1q_s32(buf);
|       |                        ^~~~~~~~~~~~~~
| ninja: build stopped: subcommand failed.
| WARNING: /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037:155 exit 1 from 'eval ${DESTDIR:+DESTDIR=${DESTDIR} }VERBOSE=1 cmake --build '/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/build' "$@" -- ${EXTRA_OECMAKE_BUILD}'
| WARNING: Backtrace (BB generated script):
|       #1: cmake_runcmake_build, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 155
|       #2: cmake_do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 149
|       #3: do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 144
|       #4: main, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 168
|
| Backtrace (metadata-relative locations):
|       #1: cmake_runcmake_build, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../poky/meta/classes/cmake.bbclass, line 205
|       #2: cmake_do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../poky/meta/classes/cmake.bbclass, line 209
|       #3: do_compile, autogenerated, line 2
ERROR: Task (/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../meta-openembedded/meta-multimedia/recipes-multimedia/aom/aom_2.0.0.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3538 tasks of which 3326 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../meta-openembedded/meta-multimedia/recipes-multimedia/aom/aom_2.0.0.bb:do_compile
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Do you have any idea why it didn't work ?

Best regards,

Safouane

Le jeu. 18 févr. 2021 à 20:54, Khem Raj <raj.khem@...> a écrit :
can you try adding

EXTRA_OECMAKE += "-DHAVE_NEON=0"

and see if that helps ? for whatever reason set_aom_detect_var is
enabling it where as default should be 0

On Thu, Feb 18, 2021 at 10:42 AM safouane maaloul
<maaloulsafouane@...> wrote:
>
> I succed in removing callconvention-hard from TUNE_FEATURES ? But i have the same problem. I am pretty sure that i get get it working if i add neon to the TUNE_FEATURES. Something like this     TUNE_FEATURES= "arm armv6 vfp arm1176jzfs callconvention-hard neon". But I can't do it with armv6. I have to use raspberrypi zero w so i have to make it work with armv6. I know that i can make it work with armv7 and armv8. I have error like this : | In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:20:
> | /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:528:24: note: called from here
> |   528 |   const int16x4_t s1 = vmovn_s32(v1);
> |       |                        ^~~~~~~~~~~~~
> | In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:12:
> | /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/recipe-sysroot-native/usr/lib/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/10.2.0/include/arm_neon.h:7556:1: error: inlining failed in call to 'always_inline' 'vmovn_s32': target specific option mismatch
> |  7556 | vmovn_s32 (int32x4_t __a)
> |       | ^~~~~~~~~
>
> So i am sure i have to add the neon feature so i appreciate it if someone can help me. I didn't find a workaround this problem on the internet.
>
> Best regards,
>
> Safouane
>
> Le jeu. 18 févr. 2021 à 18:00, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>>
>> https://yocto.yoctoproject.narkive.com/Wle40I09/gcc-on-arm
>>
>> https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-TUNE_FEATURES
>> https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-AVAILTUNES
>>
>> Zee
>> _______
>>
>> On Thu, Feb 18, 2021 at 3:28 PM safouane maaloul
>> <maaloulsafouane@...> wrote:
>> >
>> > Yes I will check it. Do you know how to remove callconvention-hard from TUNE_FEATURES ?
>> >
>> > Best regards,
>> >
>> > Safouane
>> >
>> > Le jeu. 18 févr. 2021 à 14:52, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>> >>
>> >> > TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"
>> >>
>> >> Here is an interesting reading for you, for me also:
>> >> https://www.yoctoproject.org/pipermail/meta-xilinx/2015-July/001060.html
>> >>
>> >> What I am getting from this reading is that you need to try with the
>> >> following line:
>> >> TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs"
>> >>
>> >> I guess, YOCTO people have not too much experience with armv6, nor me,
>> >> but this should be (I hope) generic.
>> >>
>> >> Hope this helps.
>> >> Zoran
>> >> _______
>> >>
>> >> On Thu, Feb 18, 2021 at 12:44 PM safouane maaloul
>> >> <maaloulsafouane@...> wrote:
>> >> >
>> >> > This is my build configuration :
>> >> > Build Configuration:
>> >> > BB_VERSION           = "1.46.0"
>> >> > BUILD_SYS            = "x86_64-linux"
>> >> > NATIVELSBSTRING      = "universal"
>> >> > TARGET_SYS           = "arm-poky-linux-gnueabi"
>> >> > MACHINE              = "raspberrypi0-wifi"
>> >> > DISTRO               = "poky"
>> >> > DISTRO_VERSION       = "3.1.5"
>> >> > TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"
>> >> > TARGET_FPU           = "hard"
>> >> > meta
>> >> > meta-poky
>> >> > meta-yocto-bsp       = "dunfell:7ea41de13774675828239b7738d3f5d70be8b1af"
>> >> > meta-oe
>> >> > meta-multimedia
>> >> > meta-networking
>> >> > meta-python          = "dunfell:5bba79488b7d393d2258d6e917f7bf7b0d7c4073"
>> >> > meta-raspberrypi     = "dunfell:987993209716302eb8f314f69a2a3340555f94d8"
>> >> > meta-gstreamer1.0    = "dunfell:b489b1ba084544d9c4c08f7c3b3d1c37ffa53c51"
>> >> >
>> >> > Best regards,
>> >> >
>> >> > Safouane
>> >> >
>> >> > Le mer. 17 févr. 2021 à 13:24, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>> >> >>
>> >> >> So, what is your MACHINE variable set to?
>> >> >>
>> >> >> Maybe knowing that, somebody can help.
>> >> >>
>> >> >> Zee
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > SAFOUANE MAALOUL
>> >> > maaloulsafouane@...
>> >> >
>> >
>> >
>> >
>> > --
>> > SAFOUANE MAALOUL
>> > maaloulsafouane@...
>> >
>
>
>
> --
> SAFOUANE MAALOUL
> maaloulsafouane@...
>
>
>
>


--
SAFOUANE MAALOUL
--
SAFOUANE MAALOUL


Khem Raj
 

Please try applying below patch to aom recipe in meta-openembedded repo

https://lists.openembedded.org/g/openembedded-devel/topic/meta_multimedia_patch_aom/80743335?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,80743335

let me know how it goes.

On Thu, Feb 18, 2021 at 12:22 PM safouane maaloul
<maaloulsafouane@gmail.com> wrote:

Sorry to annoying you with my question but how do i find where HAVE_NEON is set ?

Best regards,

Safouane

Le jeu. 18 févr. 2021 à 21:16, Khem Raj <raj.khem@gmail.com> a écrit :

Well we do not enable neon for this tune but aom still seems to want it so I would suggest to look at the build and see if it’s disabling neon and have HAVE_NEON is not set properly

On Thu, Feb 18, 2021 at 12:12 PM safouane maaloul <maaloulsafouane@gmail.com> wrote:

I have an erreur:
| /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:525:24: note: called from here
| 525 | const int32x4_t v0 = vld1q_s32(buf);
| | ^~~~~~~~~~~~~~
| ninja: build stopped: subcommand failed.
| WARNING: /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037:155 exit 1 from 'eval ${DESTDIR:+DESTDIR=${DESTDIR} }VERBOSE=1 cmake --build '/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/build' "$@" -- ${EXTRA_OECMAKE_BUILD}'
| WARNING: Backtrace (BB generated script):
| #1: cmake_runcmake_build, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 155
| #2: cmake_do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 149
| #3: do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 144
| #4: main, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 168
|
| Backtrace (metadata-relative locations):
| #1: cmake_runcmake_build, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../poky/meta/classes/cmake.bbclass, line 205
| #2: cmake_do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../poky/meta/classes/cmake.bbclass, line 209
| #3: do_compile, autogenerated, line 2
ERROR: Task (/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../meta-openembedded/meta-multimedia/recipes-multimedia/aom/aom_2.0.0.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3538 tasks of which 3326 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../meta-openembedded/meta-multimedia/recipes-multimedia/aom/aom_2.0.0.bb:do_compile
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Do you have any idea why it didn't work ?

Best regards,

Safouane

Le jeu. 18 févr. 2021 à 20:54, Khem Raj <raj.khem@gmail.com> a écrit :

can you try adding

EXTRA_OECMAKE += "-DHAVE_NEON=0"

and see if that helps ? for whatever reason set_aom_detect_var is
enabling it where as default should be 0

On Thu, Feb 18, 2021 at 10:42 AM safouane maaloul
<maaloulsafouane@gmail.com> wrote:

I succed in removing callconvention-hard from TUNE_FEATURES ? But i have the same problem. I am pretty sure that i get get it working if i add neon to the TUNE_FEATURES. Something like this TUNE_FEATURES= "arm armv6 vfp arm1176jzfs callconvention-hard neon". But I can't do it with armv6. I have to use raspberrypi zero w so i have to make it work with armv6. I know that i can make it work with armv7 and armv8. I have error like this : | In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:20:
| /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:528:24: note: called from here
| 528 | const int16x4_t s1 = vmovn_s32(v1);
| | ^~~~~~~~~~~~~
| In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:12:
| /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/recipe-sysroot-native/usr/lib/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/10.2.0/include/arm_neon.h:7556:1: error: inlining failed in call to 'always_inline' 'vmovn_s32': target specific option mismatch
| 7556 | vmovn_s32 (int32x4_t __a)
| | ^~~~~~~~~

So i am sure i have to add the neon feature so i appreciate it if someone can help me. I didn't find a workaround this problem on the internet.

Best regards,

Safouane

Le jeu. 18 févr. 2021 à 18:00, Zoran Stojsavljevic <zoran.stojsavljevic@gmail.com> a écrit :

https://yocto.yoctoproject.narkive.com/Wle40I09/gcc-on-arm

https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-TUNE_FEATURES
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-AVAILTUNES

Zee
_______

On Thu, Feb 18, 2021 at 3:28 PM safouane maaloul
<maaloulsafouane@gmail.com> wrote:

Yes I will check it. Do you know how to remove callconvention-hard from TUNE_FEATURES ?

Best regards,

Safouane

Le jeu. 18 févr. 2021 à 14:52, Zoran Stojsavljevic <zoran.stojsavljevic@gmail.com> a écrit :

TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
Here is an interesting reading for you, for me also:
https://www.yoctoproject.org/pipermail/meta-xilinx/2015-July/001060.html

What I am getting from this reading is that you need to try with the
following line:
TUNE_FEATURES = "arm armv6 vfp arm1176jzfs"

I guess, YOCTO people have not too much experience with armv6, nor me,
but this should be (I hope) generic.

Hope this helps.
Zoran
_______

On Thu, Feb 18, 2021 at 12:44 PM safouane maaloul
<maaloulsafouane@gmail.com> wrote:

This is my build configuration :
Build Configuration:
BB_VERSION = "1.46.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "raspberrypi0-wifi"
DISTRO = "poky"
DISTRO_VERSION = "3.1.5"
TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "dunfell:7ea41de13774675828239b7738d3f5d70be8b1af"
meta-oe
meta-multimedia
meta-networking
meta-python = "dunfell:5bba79488b7d393d2258d6e917f7bf7b0d7c4073"
meta-raspberrypi = "dunfell:987993209716302eb8f314f69a2a3340555f94d8"
meta-gstreamer1.0 = "dunfell:b489b1ba084544d9c4c08f7c3b3d1c37ffa53c51"

Best regards,

Safouane

Le mer. 17 févr. 2021 à 13:24, Zoran Stojsavljevic <zoran.stojsavljevic@gmail.com> a écrit :

So, what is your MACHINE variable set to?

Maybe knowing that, somebody can help.

Zee


--
SAFOUANE MAALOUL
maaloulsafouane@gmail.com


--
SAFOUANE MAALOUL
maaloulsafouane@gmail.com


--
SAFOUANE MAALOUL
maaloulsafouane@gmail.com





--
SAFOUANE MAALOUL
maaloulsafouane@gmail.com
--
SAFOUANE MAALOUL
maaloulsafouane@gmail.com


safouane maaloul
 

Yeah it works. I have yet to test the image on my raspberry pi Monday in the office. But I finished the build.  I will tested Monday and i will tell you. I have a warning : 
image-1.0-r0 do_rootfs: The license listed AOM-Patent-1.0 was not in the licenses collected for recipe aom 

I think because the name of the license in meta-openembedded/meta-multimedia/licenses/ is AOM-Patent-License-1.0 and not AOM-Patent-1.0 like mentioned in the recipe. I think it must be changed. Thanks I will tell you Monday what happened when I try the image on my raspberry Pi zero W.

Best regards,

Safouane

Le ven. 19 févr. 2021 à 00:00, Khem Raj <raj.khem@...> a écrit :
Please try applying below patch to aom recipe in meta-openembedded repo

https://lists.openembedded.org/g/openembedded-devel/topic/meta_multimedia_patch_aom/80743335?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,80743335

let me know how it goes.

On Thu, Feb 18, 2021 at 12:22 PM safouane maaloul
<maaloulsafouane@...> wrote:
>
> Sorry to annoying you with my question but how do i find where HAVE_NEON is set ?
>
> Best regards,
>
> Safouane
>
> Le jeu. 18 févr. 2021 à 21:16, Khem Raj <raj.khem@...> a écrit :
>>
>> Well we do not enable neon for this tune but aom still seems to want it so I would suggest to look at the build and see if it’s disabling neon and have HAVE_NEON is not set properly
>>
>> On Thu, Feb 18, 2021 at 12:12 PM safouane maaloul <maaloulsafouane@...> wrote:
>>>
>>> I have an erreur:
>>> | /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:525:24: note: called from here
>>> |   525 |   const int32x4_t v0 = vld1q_s32(buf);
>>> |       |                        ^~~~~~~~~~~~~~
>>> | ninja: build stopped: subcommand failed.
>>> | WARNING: /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037:155 exit 1 from 'eval ${DESTDIR:+DESTDIR=${DESTDIR} }VERBOSE=1 cmake --build '/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/build' "$@" -- ${EXTRA_OECMAKE_BUILD}'
>>> | WARNING: Backtrace (BB generated script):
>>> |       #1: cmake_runcmake_build, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 155
>>> |       #2: cmake_do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 149
>>> |       #3: do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 144
>>> |       #4: main, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 168
>>> |
>>> | Backtrace (metadata-relative locations):
>>> |       #1: cmake_runcmake_build, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../poky/meta/classes/cmake.bbclass, line 205
>>> |       #2: cmake_do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../poky/meta/classes/cmake.bbclass, line 209
>>> |       #3: do_compile, autogenerated, line 2
>>> ERROR: Task (/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../meta-openembedded/meta-multimedia/recipes-multimedia/aom/aom_2.0.0.bb:do_compile) failed with exit code '1'
>>> NOTE: Tasks Summary: Attempted 3538 tasks of which 3326 didn't need to be rerun and 1 failed.
>>>
>>> Summary: 1 task failed:
>>>   /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../meta-openembedded/meta-multimedia/recipes-multimedia/aom/aom_2.0.0.bb:do_compile
>>> Summary: There was 1 WARNING message shown.
>>> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>>>
>>> Do you have any idea why it didn't work ?
>>>
>>> Best regards,
>>>
>>> Safouane
>>>
>>> Le jeu. 18 févr. 2021 à 20:54, Khem Raj <raj.khem@...> a écrit :
>>>>
>>>> can you try adding
>>>>
>>>> EXTRA_OECMAKE += "-DHAVE_NEON=0"
>>>>
>>>> and see if that helps ? for whatever reason set_aom_detect_var is
>>>> enabling it where as default should be 0
>>>>
>>>> On Thu, Feb 18, 2021 at 10:42 AM safouane maaloul
>>>> <maaloulsafouane@...> wrote:
>>>> >
>>>> > I succed in removing callconvention-hard from TUNE_FEATURES ? But i have the same problem. I am pretty sure that i get get it working if i add neon to the TUNE_FEATURES. Something like this     TUNE_FEATURES= "arm armv6 vfp arm1176jzfs callconvention-hard neon". But I can't do it with armv6. I have to use raspberrypi zero w so i have to make it work with armv6. I know that i can make it work with armv7 and armv8. I have error like this : | In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:20:
>>>> > | /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:528:24: note: called from here
>>>> > |   528 |   const int16x4_t s1 = vmovn_s32(v1);
>>>> > |       |                        ^~~~~~~~~~~~~
>>>> > | In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:12:
>>>> > | /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/recipe-sysroot-native/usr/lib/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/10.2.0/include/arm_neon.h:7556:1: error: inlining failed in call to 'always_inline' 'vmovn_s32': target specific option mismatch
>>>> > |  7556 | vmovn_s32 (int32x4_t __a)
>>>> > |       | ^~~~~~~~~
>>>> >
>>>> > So i am sure i have to add the neon feature so i appreciate it if someone can help me. I didn't find a workaround this problem on the internet.
>>>> >
>>>> > Best regards,
>>>> >
>>>> > Safouane
>>>> >
>>>> > Le jeu. 18 févr. 2021 à 18:00, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>>>> >>
>>>> >> https://yocto.yoctoproject.narkive.com/Wle40I09/gcc-on-arm
>>>> >>
>>>> >> https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-TUNE_FEATURES
>>>> >> https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-AVAILTUNES
>>>> >>
>>>> >> Zee
>>>> >> _______
>>>> >>
>>>> >> On Thu, Feb 18, 2021 at 3:28 PM safouane maaloul
>>>> >> <maaloulsafouane@...> wrote:
>>>> >> >
>>>> >> > Yes I will check it. Do you know how to remove callconvention-hard from TUNE_FEATURES ?
>>>> >> >
>>>> >> > Best regards,
>>>> >> >
>>>> >> > Safouane
>>>> >> >
>>>> >> > Le jeu. 18 févr. 2021 à 14:52, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>>>> >> >>
>>>> >> >> > TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"
>>>> >> >>
>>>> >> >> Here is an interesting reading for you, for me also:
>>>> >> >> https://www.yoctoproject.org/pipermail/meta-xilinx/2015-July/001060.html
>>>> >> >>
>>>> >> >> What I am getting from this reading is that you need to try with the
>>>> >> >> following line:
>>>> >> >> TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs"
>>>> >> >>
>>>> >> >> I guess, YOCTO people have not too much experience with armv6, nor me,
>>>> >> >> but this should be (I hope) generic.
>>>> >> >>
>>>> >> >> Hope this helps.
>>>> >> >> Zoran
>>>> >> >> _______
>>>> >> >>
>>>> >> >> On Thu, Feb 18, 2021 at 12:44 PM safouane maaloul
>>>> >> >> <maaloulsafouane@...> wrote:
>>>> >> >> >
>>>> >> >> > This is my build configuration :
>>>> >> >> > Build Configuration:
>>>> >> >> > BB_VERSION           = "1.46.0"
>>>> >> >> > BUILD_SYS            = "x86_64-linux"
>>>> >> >> > NATIVELSBSTRING      = "universal"
>>>> >> >> > TARGET_SYS           = "arm-poky-linux-gnueabi"
>>>> >> >> > MACHINE              = "raspberrypi0-wifi"
>>>> >> >> > DISTRO               = "poky"
>>>> >> >> > DISTRO_VERSION       = "3.1.5"
>>>> >> >> > TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"
>>>> >> >> > TARGET_FPU           = "hard"
>>>> >> >> > meta
>>>> >> >> > meta-poky
>>>> >> >> > meta-yocto-bsp       = "dunfell:7ea41de13774675828239b7738d3f5d70be8b1af"
>>>> >> >> > meta-oe
>>>> >> >> > meta-multimedia
>>>> >> >> > meta-networking
>>>> >> >> > meta-python          = "dunfell:5bba79488b7d393d2258d6e917f7bf7b0d7c4073"
>>>> >> >> > meta-raspberrypi     = "dunfell:987993209716302eb8f314f69a2a3340555f94d8"
>>>> >> >> > meta-gstreamer1.0    = "dunfell:b489b1ba084544d9c4c08f7c3b3d1c37ffa53c51"
>>>> >> >> >
>>>> >> >> > Best regards,
>>>> >> >> >
>>>> >> >> > Safouane
>>>> >> >> >
>>>> >> >> > Le mer. 17 févr. 2021 à 13:24, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>>>> >> >> >>
>>>> >> >> >> So, what is your MACHINE variable set to?
>>>> >> >> >>
>>>> >> >> >> Maybe knowing that, somebody can help.
>>>> >> >> >>
>>>> >> >> >> Zee
>>>> >> >> >
>>>> >> >> >
>>>> >> >> >
>>>> >> >> > --
>>>> >> >> > SAFOUANE MAALOUL
>>>> >> >> > maaloulsafouane@...
>>>> >> >> >
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> > --
>>>> >> > SAFOUANE MAALOUL
>>>> >> > maaloulsafouane@...
>>>> >> >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > SAFOUANE MAALOUL
>>>> > maaloulsafouane@...
>>>> >
>>>> >
>>>> >
>>>> >
>>>
>>>
>>>
>>> --
>>> SAFOUANE MAALOUL
>>> maaloulsafouane@...
>>>
> --
> SAFOUANE MAALOUL
> maaloulsafouane@...
>


--
SAFOUANE MAALOUL