Date   

Run aarch64 binaries using bitbake recipe

William Jacob
 

Hi, I have a yocto build system which currently cross compiles for armv7 (32bit) .

I have a requirement of building 64 bit software .How do I modify my yocto build such that I am able to run create binaries aarch64

 

Thanks

William


Re: [ptest-runner][PATCH v2] Fix inappropriate ioctl when detaching tty

Chen Qi
 

Hi Anibal,

The ptest-runner repo seems to be messed up.
This patch is no longer there, yet the SRCREV in ptest-runner recipe refers to this commit.

$ git show 834670317bd3f6e427e1ac461c07ada6b8936dfd
fatal: bad object 834670317bd3f6e427e1ac461c07ada6b8936dfd

Regards,
Chen Qi

On 07/14/2020 03:29 AM, Anibal Limon wrote:
Applied, Thanks!.

Anibal

On Fri, 10 Jul 2020 at 00:44, Tero Kinnunen <tero.kinnunen@...> wrote:
Fixes error

    ERROR: Unable to detach from controlling tty, Inappropriate ioctl for device

when running multiple ptests

    ptest-runner a b

or when invoked over ssh single command, like

    $ ssh localhost ptest-runner

For ssh case, fd 0 is not a tty. (isatty(0) is false).
When running multiple ptests, deattach for parent needs to be
done only once.

Signed-off-by: Tero Kinnunen <tero.kinnunen@...>
---
 utils.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/utils.c b/utils.c
index a8ba190..a4e190e 100644
--- a/utils.c
+++ b/utils.c
@@ -437,6 +437,9 @@ run_ptests(struct ptest_list *head, const struct ptest_options opts,
                        break;
                }
                fprintf(fp, "START: %s\n", progname);
+               if (isatty(0) && ioctl(0, TIOCNOTTY) == -1) {
+                       fprintf(fp, "ERROR: Unable to detach from controlling tty, %s\n", strerror(errno));
+               }
                PTEST_LIST_ITERATE_START(head, p)
                        char *ptest_dir = strdup(p->run_ptest);
                        if (ptest_dir == NULL) {
@@ -444,9 +447,6 @@ run_ptests(struct ptest_list *head, const struct ptest_options opts,
                                break;
                        }
                        dirname(ptest_dir);
-                       if (ioctl(0, TIOCNOTTY) == -1) {
-                               fprintf(fp, "ERROR: Unable to detach from controlling tty, %s\n", strerror(errno));
-                       }

                        if ((pgid = getpgid(0)) == -1) {
                                fprintf(fp, "ERROR: getpgid() failed, %s\n", strerror(errno));
--
2.25.1




    



Re: #av1 #armv6 #raspberrypi #neon #av1 #armv6 #raspberrypi #neon

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


[meta-gplv2] [PATCH] disable-gplv3.inc: Update pattern match to what we really mean

Richard Purdie
 

This code wants to disable GPLv3 and GPLv3+ however the pattern
didnt specify that and with recent changes in OE-Core, it needs
to be specific. Update the pattern to be specific.

Signed-off-by: Richard Purdie <richard.purdie@...>
---
conf/distro/include/disable-gplv3.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/distro/include/disable-gplv3.inc b/conf/distro/include/disable-gplv3.inc
index 761be7d..bded378 100644
--- a/conf/distro/include/disable-gplv3.inc
+++ b/conf/distro/include/disable-gplv3.inc
@@ -1,3 +1,3 @@
-INCOMPATIBLE_LICENSE = '*GPLv3'
+INCOMPATIBLE_LICENSE = '*GPLv3*'
WARN_QA_remove = 'incompatible-license'
RDEPENDS_${PN}-ptest_remove_pn-glib-2.0 = "python3-dbusmock"
--
2.27.0


Re: #av1 #armv6 #raspberrypi #neon #av1 #armv6 #raspberrypi #neon

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@...> 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@...


Re: #av1 #armv6 #raspberrypi #neon #av1 #armv6 #raspberrypi #neon

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


Re: #av1 #armv6 #raspberrypi #neon #av1 #armv6 #raspberrypi #neon

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


Re: #av1 #armv6 #raspberrypi #neon #av1 #armv6 #raspberrypi #neon

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


Re: #av1 #armv6 #raspberrypi #neon #av1 #armv6 #raspberrypi #neon

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@...> 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@...




Re: #av1 #armv6 #raspberrypi #neon #av1 #armv6 #raspberrypi #neon

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


Re: [meta-selinux][PATCH] remove obsolete e2fsprogs bbappend

Randy MacLeod
 

On 2021-02-08 1:32 a.m., hongxu wrote:
Since oe-core commit [f51835e022 e2fsprogs: upgrade 1.45.6 -> 1.45.7] applied,
the backport misc_create_inode.c-label_rootfs.patch is not required
The lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch is not used by the recipe,
so also remove it.
Signed-off-by: Hongxu Jia <hongxu.jia@...>
Ping Joe...

../Randy

---
.../e2fsprogs/e2fsprogs_%.bbappend | 1 -
.../e2fsprogs/e2fsprogs_selinux.inc | 3 --
...t2fs-ext2_ext_attr.h-add-xattr-index.patch | 20 ---------
.../misc_create_inode.c-label_rootfs.patch | 45 -------------------
4 files changed, 69 deletions(-)
delete mode 100644 recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
delete mode 100644 recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
delete mode 100644 recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
delete mode 100644 recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch
diff --git a/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend b/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
deleted file mode 100644
index 7719d3b..0000000
--- a/recipes-devtools/e2fsprogs/e2fsprogs_%.bbappend
+++ /dev/null
@@ -1 +0,0 @@
-require ${@bb.utils.contains('DISTRO_FEATURES', 'selinux', '${BPN}_selinux.inc', '', d)}
diff --git a/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc b/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
deleted file mode 100644
index 9cbb7fe..0000000
--- a/recipes-devtools/e2fsprogs/e2fsprogs_selinux.inc
+++ /dev/null
@@ -1,3 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
-
-SRC_URI += "file://misc_create_inode.c-label_rootfs.patch"
diff --git a/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch b/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
deleted file mode 100644
index b87c414..0000000
--- a/recipes-devtools/e2fsprogs/files/lib-ext2fs-ext2_ext_attr.h-add-xattr-index.patch
+++ /dev/null
@@ -1,20 +0,0 @@
-Add xattr name index for xattrs with the 'security' prefix. These are defined
-in the ext(2|3|4)/xattr.h in the kernel. We use the EXT2 prefix for consistency
-with e2fslibs naming.
-
-Signed-off-by: Philip Tricca <flihp@...>
-
-Index: e2fsprogs-1.42.9/lib/ext2fs/ext2_ext_attr.h
-===================================================================
---- e2fsprogs-1.42.9.orig/lib/ext2fs/ext2_ext_attr.h
-+++ e2fsprogs-1.42.9/lib/ext2fs/ext2_ext_attr.h
-@@ -15,6 +15,9 @@
- /* Maximum number of references to one attribute block */
- #define EXT2_EXT_ATTR_REFCOUNT_MAX 1024
-
-+/* Name indexes */
-+#define EXT2_XATTR_INDEX_SECURITY 6
-+
- struct ext2_ext_attr_header {
- __u32 h_magic; /* magic number for identification */
- __u32 h_refcount; /* reference count */
diff --git a/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch b/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch
deleted file mode 100644
index 046e521..0000000
--- a/recipes-devtools/e2fsprogs/files/misc_create_inode.c-label_rootfs.patch
+++ /dev/null
@@ -1,45 +0,0 @@
-From: Philip Tricca <flihp@...>
-To: tytso@...
-Cc: liezhi.yang@...
-Date: Sat, 20 Feb 2016 18:58:58 +0000
-Subject: [PATCH] misc/create_inode.c: Copy xattrs from root directory when populating fs.
-
-When copying a file system using the -d option the xattrs from the root
-directory need to be copied before the populate_fs recusion starts.
-
-Signed-off-by: Philip Tricca <flihp@...>
-Signed-off-by: Jeremy Puhlman <jpuhlman@...>
-
----
- misc/create_inode.c | 8 ++++++++
- 1 file changed, 8 insertions(+)
-
-diff --git a/misc/create_inode.c b/misc/create_inode.c
-index a7b6d348..cfd15922 100644
---- a/misc/create_inode.c
-+++ b/misc/create_inode.c
-@@ -979,6 +979,13 @@ errcode_t populate_fs2(ext2_filsys fs, ext2_ino_t parent_ino,
- return retval;
- }
-
-+ retval = set_inode_xattr(fs, root, source_dir);
-+ if (retval) {
-+ com_err(__func__, retval,
-+ _("while setting xattrs for \"%s\""), source_dir);
-+ goto out;
-+ }
-+
- file_info.path_len = 0;
- file_info.path_max_len = 255;
- file_info.path = calloc(file_info.path_max_len, 1);
-@@ -987,6 +994,7 @@ errcode_t populate_fs2(ext2_filsys fs, ext2_ino_t parent_ino,
- &file_info, fs_callbacks);
-
- free(file_info.path);
-+out:
- free(hdlinks.hdl);
- return retval;
- }
---
-2.11.1
-

--
# Randy MacLeod
# Wind River Linux


Re: #av1 #armv6 #raspberrypi #neon #av1 #armv6 #raspberrypi #neon

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@...> 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@...


Re: #av1 #armv6 #raspberrypi #neon #av1 #armv6 #raspberrypi #neon

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


Re: [qa-build-notification] [yocto] QA notification for completed autobuilder build (yocto-3.2.2.rc1)

Richard Purdie
 

On Thu, 2021-02-18 at 14:58 +0100, Yann Dirson wrote:


Le mar. 16 févr. 2021 à 18:43, Pokybuild User <pokybuild@...> a écrit :

Build hash information:

bitbake: 0a3bf681530bd63fc0036ca81ef868ab53fde56c
meta-arm: aa63e31b6edb5197764c21434219050ab51f0fbd
meta-gplv2: 6e8e969590a22a729db1ff342de57f2fd5d02d43
meta-intel: 1d866c58534eb1d317b7a674c6e6c57ab9594fb0
meta-kernel: f793168bd19af3d8c5a260dd35f387ed9a31794b
meta-mingw: 352d8b0aa3c7bbd5060a4cc2ebe7c0e964de4879
oecore: ebaaee50cb3ac75112827f935c48affaf622ce7f
poky: d5d6286a66f46f4523e35e0e3f20cd7396195fdc
Is it expected that the noted meta-arm sha1 is on branch "master" and not "gatesgarth" ?
Not expected but we worked it out. There is a patch from Ross on
this list which fixes the issue in yocto-autobuilder2. For the 
purposes of the release I'm thinking we should rerun the meta-arm 
tests and swap in the gatesgarth revision.

Copying Vineela/Michael so they know about the issue.

Cheers,

Richard


Re: QA notification for completed autobuilder build (yocto-3.2.2.rc1)

Yann Dirson
 



Le mar. 16 févr. 2021 à 18:43, Pokybuild User <pokybuild@...> a écrit :

Build hash information:

bitbake: 0a3bf681530bd63fc0036ca81ef868ab53fde56c
meta-arm: aa63e31b6edb5197764c21434219050ab51f0fbd
meta-gplv2: 6e8e969590a22a729db1ff342de57f2fd5d02d43
meta-intel: 1d866c58534eb1d317b7a674c6e6c57ab9594fb0
meta-kernel: f793168bd19af3d8c5a260dd35f387ed9a31794b
meta-mingw: 352d8b0aa3c7bbd5060a4cc2ebe7c0e964de4879
oecore: ebaaee50cb3ac75112827f935c48affaf622ce7f
poky: d5d6286a66f46f4523e35e0e3f20cd7396195fdc

Is it expected that the noted meta-arm sha1 is on branch "master" and not "gatesgarth" ?


Re: #av1 #armv6 #raspberrypi #neon #av1 #armv6 #raspberrypi #neon

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@...> 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@...


Re: Keep .bbappend for older Yocto version

Jonas Vautherin
 

It does help, yes!
Thanks a lot!

On Thu, 18 Feb 2021, 12:24 , <Mikko.Rapeli@...> wrote:
Hi,

On Wed, Feb 17, 2021 at 12:02:26AM +0100, Jonas Vautherin wrote:
> Good evening,
>
> I am using Yocto Gatesgarth, and I was just updating a layer that was
> written for Dunfell. In the `conf/layer.conf`, I can simply add
> "gatesgarth" to `LAYERSERIES_COMPAT_pocketbeagle`, like so:
>
> ```
> LAYERSERIES_COMPAT_pocketbeagle = "dunfell gatesgarth"
> ```
>
> However, this does not seem to work for a `.bbappend`. Let me use this
> particular layer as an example: it is a BSP that defines
> `linux-yocto_4.19.bbappend` for Dunfell. In my case, I want to define
> `linux-yocto_5.4.bbappend` for Gatesgarth. When building with Dunfell, I
> would like it to use the former, and when building with Gatesgarth, I would
> like it to use the latter.
>
> However, if I keep both `linux-yocto_4.19.bbappend`
> and `linux-yocto_5.4.bbappend` and try to build with Gatesgarth, it fails
> with:
>
> ```
> ERROR: No recipes in default available for:
>   /path/to/recipes-kernel/linux/linux-yocto_4.19.bbappend
> ```
>
> Which makes sense: Gatesgarth does not provide `linux-yocto_4.19`.
>
> Is there a way to keep both `*.bbappend` and have Yocto ignore the ones
> that do not correspond to its version? Or would that be bad practice anyway?

What I do in cases like this:

 * check and decide if BSP layer can be update to be fully compatible with new yocto
   version, by asking from maintainers of the BSP layer and HW vendors
   (usual answer is 'not this year, maybe next' or 'if you pay?', if you are lucky
    they will say 'just use the correct branch')

 * check if simple patches can update BSP layer to be compatible with new yocto
   version, if this involves Linux kernel, libdrm etc major version changes it
   might not work

Quite often, I keep using the BSP SW stack from old yocto release with only minimal
changes. For this to work, I make the minimal modifications needed to support building
with new yocto version like modify LAYERSERIES_COMPAT and adapt bbclasses, then copy
the needed old recipes from previous yocto version over the the BSP layer to be
maintained there by the BSP SW maintainers. What helps a lot, is that you have
reviewed what SW components you need to use from BSP SW meta layer and you have
BBMASK'ed away all recipes and bbappends which your product and its distro
configuration does not need.

Often BSP layers are full of examples, prototypes, or just plain weird changes
to high level SW components like gstreamer, systemd, openssl or openssh which your
product might not need (e.g. is prefectly fine with the poky version of the recipe).
These BSP side changes make yocto updates much more difficult and versioned dependencies
from BSP to poky are too complex and difficult to resolve easily. Thus look
for minimizing the impact of the BSP SW stack, keep it unchanged apart from minimal
bitbake and bbclass fixes, and update the rest.

For security and other updates, the BSP SW stack needs to be handled separately.

Hope this helps,

-Mikko


Re: #av1 #armv6 #raspberrypi #neon #av1 #armv6 #raspberrypi #neon

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


Re: #av1 #armv6 #raspberrypi #neon #av1 #armv6 #raspberrypi #neon

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


[meta-zephyr][PATCH 2/2] zephyr-kernel-src.inc: set default preferred version to 2.5.0

Naveen Saini
 

Signed-off-by: Naveen Saini <naveen.kumar.saini@...>
---
recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
index 2dcde74..39cbc10 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
@@ -2,7 +2,7 @@ LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://LICENSE;md5=fa818a259cbed7ce8bc2a22d35a464fc"

# Default to a stable version
-PREFERRED_VERSION_zephyr-kernel ??= "2.4.0"
+PREFERRED_VERSION_zephyr-kernel ??= "2.5.0"
include zephyr-kernel-src-${PREFERRED_VERSION_zephyr-kernel}.inc

inherit cmake
--
2.17.1

5021 - 5040 of 57387