Re: [oe-core][PATCH] graphene: disable neon support on arm 32bits

Am Sa, 11. Feb 2023 um 09:05:05 + schrieb Richard Purdie : Can we tweak the comment to say why? Saying what it does isn't that useful, saying why it does it helps to understand when it may be removed in future. An example of how to crash it would be even better. Was this just some some subset

[OE-core][dunfell][PATCH] git: Whitelist CVE-2022-41953

From: Virendra Thakur Whitelist CVE-2022-41953 as its specific to Git-for-Windows Link: https://github.com/git-for-windows/git/security/advisories/GHSA-v4px-mx59-w99c Upstream-Status: Pending Issue: MGUBSYS-6605 Change-Id: Id9dde20c1c1b8244a7dc11e3eae0927d1604e7fd Signed-off-by: Virendra Tha

[oe-core][PATCH] graphene: add a PACKAGECONFIG for arm_neon

Not all arm platforms support neon and runtime detection for this feature is currently not reliable. Add a PACKAGECONFIG that disables neon support for arm but can be manually enabled. Signed-off-by: Markus Volk --- meta/recipes-graphics/graphene/graphene_1.10.8.bb | 1 + 1 file changed, 1 inser

Re: [oe-core][PATCH] graphene: disable neon support on arm 32bits

sent a patch for it maybe it would be better to add this as a PACKAGECONFIG, so people could at least manually enable neon support if they know it would be working for them? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177090): https://list

[oe-core][PATCHv2] graphene: add a PACKAGECONFIG for arm_neon

Not all arm platforms support neon and runtime detection for this feature is currently not reliable. Add a PACKAGECONFIG that disables neon support for arm but can be manually enabled. Enable neon for aarch64 by default Signed-off-by: Markus Volk --- meta/recipes-graphics/graphene/graphene_1.10

Re: [oe-core][PATCHv2] graphene: add a PACKAGECONFIG for arm_neon

v2 enables neon for aarch64 by default Am Mo, 13. Feb 2023 um 11:39:39 +0100 schrieb Markus Volk : Not all arm platforms support neon and runtime detection for this feature is currently not reliable. Add a PACKAGECONFIG that disables neon support for arm but can be manually enabled. Enable n

[oe-core][PATCHv3] graphene: add a PACKAGECONFIG for arm_neon

Not all arm platforms support neon and runtime detection for this feature is currently not reliable. Add a PACKAGECONFIG that disables neon support for arm but can be manually enabled. Enable neon for aarch64 by default Signed-off-by: Markus Volk --- meta/recipes-graphics/graphene/graphene_1.10

Re: [oe-core][PATCHv2] graphene: add a PACKAGECONFIG for arm_neon

I think it's commented out? Alex On Mon, 13 Feb 2023 at 11:40, Markus Volk wrote: > > v2 enables neon for aarch64 by default > > Am Mo, 13. Feb 2023 um 11:39:39 +0100 schrieb Markus Volk : > > Not all arm platforms support neon and runtime detection for this feature is > currently not reliable.

Re: [oe-core][PATCHv2] graphene: add a PACKAGECONFIG for arm_neon

Am Mo, 13. Feb 2023 um 11:43:55 +0100 schrieb Alexander Kanavin : I think it's commented out? yes, did this for testing purpose. Sorry. Sent a v3 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177095): https://lists.openembedded.org/g/openembe

Re: [oe-core][PATCHv3] graphene: add a PACKAGECONFIG for arm_neon

Doesn't this negate 'introspection' assigned with ?= ? Can you verify the final value on aarch64? (yes, this is a never-ending confusion, and I don't know how that works either, after all the years of dealing with it). Alex On Mon, 13 Feb 2023 at 11:42, Markus Volk wrote: > > Not all arm platfo

Re: [oe-core][PATCHv3] graphene: add a PACKAGECONFIG for arm_neon

Am Mo, 13. Feb 2023 um 11:45:45 +0100 schrieb Alexander Kanavin : Can you verify the final value on aarch64? You are absolutely right. ?= negates the introspection. I wasn't expecting that and was just checking to see if neon was properly activated. What would be the best way to handle this?

Re: [oe-core][PATCHv3] graphene: add a PACKAGECONFIG for arm_neon

Am Mo, 13. Feb 2023 um 12:00:08 +0100 schrieb Markus Volk : just remove the '?' No. That didn't help either. The only way that seems to work for me is: PACKAGECONFIG:append:aarch64 = " neon" -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#17709

Re: [oe-core][PATCHv3] graphene: add a PACKAGECONFIG for arm_neon

Does enabling neon break the build on non-aarch64? If not, then it could just be added to the default weak set. Otherwise, PACKAGECONFIG:append:aarch64 = " neon" seems most sensible. It can still be undone with :remove (which is ugly but possible). Alex On Mon, 13 Feb 2023 at 12:25, Markus Volk

Re: [oe-core][PATCHv3] graphene: add a PACKAGECONFIG for arm_neon

Am Mo, 13. Feb 2023 um 12:30:42 +0100 schrieb Alexander Kanavin : Does enabling neon break the build on non-aarch64? As far as I know it breaks runtime for some armv7 tunes and will probably also break build for older arm platforms that do not support neon at all. That would also work: PACK

Re: [oe-core][PATCHv3] graphene: add a PACKAGECONFIG for arm_neon

This seems best. There are numerous places in core where something similar is used. Alex On Mon, 13 Feb 2023 at 12:37, Markus Volk wrote: > > Am Mo, 13. Feb 2023 um 12:30:42 +0100 schrieb Alexander Kanavin > : > > Does enabling neon break the build on non-aarch64? > > > As far as I know it brea

[oe-core][PATCHv4] graphene: add a PACKAGECONFIG for arm_neon

Not all arm platforms support neon and runtime detection for this feature is currently not reliable. Add a PACKAGECONFIG that disables neon support for arm but can be manually enabled. Enable neon for aarch64 by default Signed-off-by: Markus Volk --- meta/recipes-graphics/graphene/graphene_1.10

Re: [oe-core][PATCHv4] graphene: add a PACKAGECONFIG for arm_neon

On 13/02/2023 13:04, Markus Volk wrote: > Not all arm platforms support neon and runtime detection for this feature is > currently not reliable. Add a PACKAGECONFIG that disables neon support for arm > but can be manually enabled. > > Enable neon for aarch64 by default > > Signed-off-by: Markus

Re: [oe-core][PATCHv4] graphene: add a PACKAGECONFIG for arm_neon

On 2/13/23 13:04, Markus Volk wrote: Not all arm platforms support neon and runtime detection for this feature is currently not reliable. Add a PACKAGECONFIG that disables neon support for arm but can be manually enabled. Enable neon for aarch64 by default Signed-off-by: Markus Volk --- met

Re: [OE-core] [PATCH 2/2] barebox-tools: add initial barebox tools support

Hello Alexandre, On 03.02.23 19:11, Alexandre Belloni via lists.openembedded.org wrote: > Hello, > > kwboot fails with musl: Thanks for relaying the autobuilder errors. I'll build with musl and see what needs to be fixed on the barebox side. > > | CC [U] scripts/kwboot-target > | In file in

[oe-core][PATCHv5] graphene: add a PACKAGECONFIG for arm_neon

Not all arm platforms support neon and runtime detection for this feature is currently not reliable. Disable neon support by default on ARM-32 platforms because of the following upstream bug: https://github.com/ebassi/graphene/issues/215 Enable neon for aarch64 by default Signed-off-by: Markus Vo

Re: [oe-core][PATCHv4] graphene: add a PACKAGECONFIG for arm_neon

Am Mo, 13. Feb 2023 um 16:31:51 +0100 schrieb Carlos Alberto Lopez Perez : Can you please add a comment in the .bb file with a note saying that Neon support gets disabled by default on ARM-32 platforms because of the following upstream bug: ?

Re: [oe-core][PATCHv4] graphene: add a PACKAGECONFIG for arm_neon

Am Mo, 13. Feb 2023 um 17:14:16 +0100 schrieb Bastian Krause : 0e0849cd1 ("graphene: disable neon support on arm 32bits") from meta-oe needs to be reverted to make this patch work, right? I guess we need to completely remove the recipe from meta-oe but I already sent a patch for that -=-=-

[OE-core] [PATCH] create-spdx-2.2: Add support for custom Annotations

This change adds a new variable to track which recipe variables are added as SPDX Annotations. Usage: add SPDX_CUSTOME_ANNOTATION_VARS = The recipe spdx json will contain an annotation stanza that looks something like this: "annotations": [ { "annotationDate": "2023-02-13

Re: [OE-core] [PATCH] create-spdx-2.2: Add support for custom Annotations

On Mon, Feb 13, 2023 at 1:54 PM Saul Wold wrote: > > This change adds a new variable to track which recipe variables > are added as SPDX Annotations. > > Usage: add SPDX_CUSTOME_ANNOTATION_VARS = nit: CUSTOM > > The recipe spdx json will contain an annotation stanza that looks > something like

[OE-core] [PATCH 1/3] unfs3: Add missing header files

These enable builds with additional warnings as errors Signed-off-by: Khem Raj --- .../unfs3/0001-fix-building-on-macOS.patch| 27 +++ meta/recipes-devtools/unfs3/unfs3_git.bb | 1 + 2 files changed, 28 insertions(+) create mode 100644 meta/recipes-devtools/unfs3/unfs

[OE-core] [PATCH 2/3] stress-ng: Add missing header files for clock_adjtime

Signed-off-by: Khem Raj --- ...nclude-sys-futex.h-for-clock_adjtime.patch | 32 +++ .../stress-ng/stress-ng_0.15.03.bb| 1 + 2 files changed, 33 insertions(+) create mode 100644 meta/recipes-extended/stress-ng/stress-ng/0001-Include-sys-futex.h-for-clock_adjtime.pat

[OE-core] [PATCH 3/3] gstreamer1.0-plugins-good: Fix build with musl

musl's definition of ioctl() API is different from glibc's and gst has built upon definition from glibc which was being warned about but now compilers can check signatures of funciton pointers, means it becomes an error with clang16+ Signed-off-by: Khem Raj --- ...ine-ioctl_req_t-for-posix-linux

Re: [oe-core][PATCH] graphene: disable neon support on arm 32bits

On 13/02/2023 10:47:19+0100, Markus Volk wrote: > Am Sa, 11. Feb 2023 um 09:05:05 + schrieb Richard Purdie > : > > Can we tweak the comment to say why? Saying what it does isn't that > > useful, saying why it does it helps to understand when it may be > > removed in future. An example of how to

Re: [oe-core][PATCHv5] graphene: add a PACKAGECONFIG for arm_neon

On 13/02/2023 19:03, Markus Volk wrote: > Not all arm platforms support neon and runtime detection for this feature is > currently not reliable. > Disable neon support by default on ARM-32 platforms because of the > following upstream bug: https://github.com/ebassi/graphene/issues/215 > > Enable n

[OE-core] Yocto Project Newcomer & Unassigned Bugs - Help Needed

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newc

[OE-core] Current high bug count owners for Yocto Project 4.2

All, Below is the list as of top 30 bug owners as of the end of WW06 of who have open medium or higher bugs and enhancements against YP 4.2. There are 52 possible work days left until the final release candidates for YP 4.2 needs to be released. Who Count michael.opdenac...@bootlin.com 34

Re: [OE-core] [PATCH] libcap: upgrade 2.66 -> 2.67

On 13/02/2023 10:42:02+0800, wangmy wrote: > From: Wang Mingyu > > License-Update: > Add description: # +/* SPDX-License-Identifier: BSD-3-Clause OR GPL-2.0-only > */ > > Signed-off-by: Wang Mingyu > --- > .../recipes-support/libcap/{libcap_2.66.bb => libcap_2.67.bb} | 4 ++-- > 1 file chang

Re: [OE-core] [PATCH 1/2] rust-android-sparse: add lightweight simg2img/img2simg implementation

On Sat, 11 Feb 2023 at 19:10, Alexander Kanavin wrote: > > But is it necessary or desirable to have it in core? This does seem > like something that belongs in meta-oe rather. My goal was to move sparse image handling in a way to be able to generate them from the BSP layers, removing dependency o

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

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.23.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. NUC 7 3. ADL 4.

Re: [oe-core][PATCH] graphene: disable neon support on arm 32bits

Am Mo, 13. Feb 2023 um 22:06:57 +0100 schrieb Alexandre Belloni via lists.openembedded.org : Can't we get that out of the tune? The problem I see is that we would need to know for sure what works and what doesn't. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group.

Re: [OE-core] [PATCH 1/2] rust-android-sparse: add lightweight simg2img/img2simg implementation

On Tue, 14 Feb 2023 at 04:42, Dmitry Baryshkov wrote: > My goal was to move sparse image handling in a way to be able to > generate them from the BSP layers, removing dependency on the meta-oe > layer. This way it is possible to generate sparse images > unconditionally and then let the user feed t

[oe-core][PATCHv6] graphene: add a PACKAGECONFIG for arm_neon

Not all arm platforms support neon and runtime detection for this feature is currently not reliable. Disable neon support by default on ARM-32 platforms because of the following upstream bug: https://github.com/ebassi/graphene/issues/215 Enable neon for aarch64 by default Signed-off-by: Markus Vo