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
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
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 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
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
wrote:
> I have an erreur:
> |
>
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:
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
wrote:
>
> I succed in removing callconvention-hard from TUNE_FEATURES ? But i have
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
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
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.stojsavlje...@gmail.com> a écrit :
> > TUNE_FEATURES= "arm armv6 vfp arm1176jzfs callconvention-hard"
>
> Here is an
> 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:
Le jeu. 18 févr. 2021 à 12:44, safouane maaloul
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
Le mer. 17 févr. 2021 à 13:18, safouane maaloul
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 <
>
So, what is your MACHINE variable set to?
Maybe knowing that, somebody can help.
Zee
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52362): https://lists.yoctoproject.org/g/yocto/message/52362
Mute This Topic:
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
14 matches
Mail list logo
