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

#av1 #armv6 #raspberrypi #neon

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%2Fsti

#av1 #armv6 #raspberrypi #neon

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

#av1 #armv6 #raspberrypi #neon

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

#av1 #armv6 #raspberrypi #neon

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 | cons

#av1 #armv6 #raspberrypi #neon

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 <maaloulsafouane@...> wrote:

#av1 #armv6 #raspberrypi #neon

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_FEATU

#av1 #armv6 #raspberrypi #neon

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-manua

#av1 #armv6 #raspberrypi #neon

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

#av1 #armv6 #raspberrypi #neon

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 follo

#av1 #armv6 #raspberrypi #neon

#av1 #armv6 #raspberrypi #neon

#av1 #armv6 #raspberrypi #neon

So, what is your MACHINE variable set to? Maybe knowing that, somebody can help. Zee

#av1 #armv6 #raspberrypi #neon

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'

#av1 #armv6 #raspberrypi #neon

Oops, I see that Khem has replied to a later email.

#yocto #gstreamer #aom #av1

Bonjour Safouane.Maaloul, Did you figure this out? The Yocto email list is >99.99% English so please consider translating before posting: Google translate says: I don't use gstreamer but if you answer

#yocto #gstreamer #aom #av1

write a gstreamer1.0-plugins-bad_%.bbappend with PACKAGECONFIG_append = " aom" Then add gstreamer1.0-plugins-bad-aom to IMAGE_INSTALL <maaloulsafouane@...> wrote:

#aom #av1 #yocto #gstreamer

Hello, I wanted to know how to add Alliance for Open Media - AV1 Codec Library (aom-plugins) gstreamer1.0-plugins-bad recipe to my image ? the Alliance for Open Media - AV1 Codec Library are in the ao

#aom #av1 #yocto #gstreamer

Bonjour, j'essaye d'ajouter le aom plugin au niveau de la gstreamer1.0-plugins-bad. J'ai basculé sur gatesgarth version. Je commence à faire lebuild. J'avais un problème de lisence. Je l'ai résolu. Et

#yocto #gstreamer #aom #av1

Bonjour, j'essaye d'ajouter le aom plugin au niveau de la gstreamer1.0-plugins-bad. J'ai basculé sur gatesgarth version. Je commence à faire lebuild. J'avais un problème de lisence. Je l'ai résolu. Et

#yocto #gstreamer #aom #av1