Signed-off-by: Naveen 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/recip
Release notes:
https://github.com/zephyrproject-rtos/zephyr/releases/tag/zephyr-v2.5.0
Signed-off-by: Naveen Saini
---
...r-kernel-src-2.5.0-rc4.inc => zephyr-kernel-src-2.5.0.inc} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename recipes-kernel/zephyr-kernel/{zephyr-kernel-src-2
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 <
> zoran.stojsavlje..
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
It does help, yes!
Thanks a lot!
On Thu, 18 Feb 2021, 12:24 , 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
> 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
Le mar. 16 févr. 2021 à 18:43, Pokybuild User <
pokybu...@centos8-ty-1.yocto.io> a écrit :
>
> Build hash information:
>
> bitbake: 0a3bf681530bd63fc0036ca81ef868ab53fde56c
> meta-arm: aa63e31b6edb5197764c21434219050ab51f0fbd
> meta-gplv2: 6e8e969590a22a729db1ff342de57f2fd5d02d43
> meta-intel: 1d8
On Thu, 2021-02-18 at 14:58 +0100, Yann Dirson wrote:
>
>
> Le mar. 16 févr. 2021 à 18:43, Pokybuild User
> a écrit :
> >
> > Build hash information:
> >
> > bitbake: 0a3bf681530bd63fc0036ca81ef868ab53fde56c
> > meta-arm: aa63e31b6edb5197764c21434219050ab51f0fbd
> > meta-gplv2: 6e8e969590a22
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
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
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
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
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 th
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
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:
> |
> /workdir/tep-cam-rpi-yocto/rpi-
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 disabli
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
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
---
conf/distro/include/disable-gplv3.inc | 2 +-
1 file changed, 1 insertion(+), 1 del
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 th
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
20 matches
Mail list logo
