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

[Markus Volk]

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 Volk 
---
 meta/recipes-graphics/graphene/graphene_1.10.8.bb | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-graphics/graphene/graphene_1.10.8.bb 
b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
index 813ff74adf..75c8258d99 100644
--- a/meta/recipes-graphics/graphene/graphene_1.10.8.bb
+++ b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
@@ -10,8 +10,12 @@ inherit gnomebase gobject-introspection gtk-doc
 SRC_URI[archive.sha256sum] = 
"a37bb0e78a419dcbeaa9c7027bcff52f5ec2367c25ec859da31dfde2928f279a"
 
 # gtk4 & mutter 41.0 requires graphene build with introspection
-PACKAGECONFIG ?= "introspection"
+# Disable neon support by default on ARM-32 platforms because of the
+# following upstream bug: https://github.com/ebassi/graphene/issues/215
+PACKAGECONFIG ?= "introspection ${@bb.utils.contains('TUNE_FEATURES', 
'aarch64', 'neon', '', d)}"
+
 PACKAGECONFIG[introspection] = 
"-Dintrospection=enabled,-Dintrospection=disabled,"
+PACKAGECONFIG[neon] = "-Darm_neon=true,-Darm_neon=false,"
 
 GTKDOC_MESON_OPTION = "gtk_doc"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177121): 
https://lists.openembedded.org/g/openembedded-core/message/177121
Mute This Topic: https://lists.openembedded.org/mt/96954386/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexander Kanavin]

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 them to fastboot.
>
> But yeah, if it's recommended to keep it in meta-oe, I can move my recipe 
> there.

Just to clarify, to get something into core, you need to explain what
are those 'android sparse images', what is consuming them, and whether
supporting them fulfils a broadly useful scenario (this is the hardest
part, as there has not been interest from others). There should also
be testing, and commitment to maintain the pieces.

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177123): 
https://lists.openembedded.org/g/openembedded-core/message/177123
Mute This Topic: https://lists.openembedded.org/mt/96898285/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Markus Volk]

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.
View/Reply Online (#177122): 
https://lists.openembedded.org/g/openembedded-core/message/177122
Mute This Topic: https://lists.openembedded.org/mt/96893757/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Jing Hui Tham]

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. TGL NUC 11
5. Edgerouter
6. Beaglebone
 
ETA for completion Friday, 17 February 2023.
 
Best regards,
Jing Hui



> -Original Message-
> From: qa-build-notificat...@lists.yoctoproject.org  notificat...@lists.yoctoproject.org> On Behalf Of Pokybuild User
> Sent: Monday, 13 February, 2023 9:22 PM
> To: yo...@lists.yoctoproject.org
> Cc: qa-build-notificat...@lists.yoctoproject.org
> Subject: [qa-build-notification] QA notification for completed autobuilder
> build (yocto-3.1.23.rc1)
> 
> 
> A build flagged for QA (yocto-3.1.23.rc1) was completed on the autobuilder
> and is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-3.1.23.rc1
> 
> 
> Build hash information:
> 
> bitbake: c16d364dbf68d2a500fecaf8d6e6d62b11475d9f
> meta-agl: ae982d798a979ee5690bee00ca90a2855bab4802
> meta-arm: b1fe8443a7a72c65fa0fc3371f607c6671b3a882
> meta-aws: 99e30a393f980694bf46284521b137eddd6a753a
> meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
> meta-intel: 6c202291925bb179d2d08b5bde80192f9b032b88
> meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
> meta-openembedded: e707e9b7cf5c62bff4fee029965a87b22dd4ccba
> meta-virtualization: beea119eb529b4a11f266004aee8b548427aea39
> oecore: daaee6fcb0d201f041678af433d8e1cd6f924d09
> poky: aec83663aadc871354b441eef0a3a41eb3780b13
> 
> 
> 
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.pur...@linuxfoundation.org
> 
> 
> 
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177120): 
https://lists.openembedded.org/g/openembedded-core/message/177120
Mute This Topic: https://lists.openembedded.org/mt/96952976/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Dmitry Baryshkov]

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 on the meta-oe
layer. This way it is possible to generate sparse images
unconditionally and then let the user feed them to fastboot.

But yeah, if it's recommended to keep it in meta-oe, I can move my recipe there.

>
> Alex
>
> On Sat, 11 Feb 2023 at 16:38, Dmitry Baryshkov  wrote:
> >
> > The Android's simg2img/img2simg comes from android-tools, which is a
> > huge package with lots of dependencies on its own. It resides inside
> > meta-oe rather than OE-Core. Add lightweight tool to handle sparse
> > images, which is small enough to be pushed into OE-Core.
> >
> > Signed-off-by: Dmitry Baryshkov 
> > ---
> >  .../rust-android-sparse_0.6.0.bb  | 68 +++
> >  1 file changed, 68 insertions(+)
> >  create mode 100644 
> > meta/recipes-extended/rust-android-sparse/rust-android-sparse_0.6.0.bb
> >
> > diff --git 
> > a/meta/recipes-extended/rust-android-sparse/rust-android-sparse_0.6.0.bb 
> > b/meta/recipes-extended/rust-android-sparse/rust-android-sparse_0.6.0.bb
> > new file mode 100644
> > index ..83652b9d452f
> > --- /dev/null
> > +++ b/meta/recipes-extended/rust-android-sparse/rust-android-sparse_0.6.0.bb
> > @@ -0,0 +1,68 @@
> > +# Auto-Generated by cargo-bitbake 0.3.16
> > +#
> > +inherit cargo
> > +
> > +# how to get android-sparse could be as easy as but default to a git 
> > checkout:
> > +SRC_URI += "crate://crates.io/android-sparse/0.6.0"
> > +S= "${CARGO_VENDORING_DIRECTORY}/android-sparse-${PV}"
> > +
> > +# please note if you have entries that do not begin with crate://
> > +# you must change them to how that package can be fetched
> > +SRC_URI += " \
> > +crate://crates.io/aho-corasick/0.7.18 \
> > +crate://crates.io/assert_cmd/0.9.1 \
> > +crate://crates.io/autocfg/1.0.1 \
> > +crate://crates.io/bitflags/1.3.2 \
> > +crate://crates.io/build_const/0.2.2 \
> > +crate://crates.io/byteorder/1.4.3 \
> > +crate://crates.io/cfg-if/1.0.0 \
> > +crate://crates.io/clap/2.34.0 \
> > +crate://crates.io/crc/1.8.1 \
> > +crate://crates.io/difference/2.0.0 \
> > +crate://crates.io/escargot/0.3.1 \
> > +crate://crates.io/float-cmp/0.4.0 \
> > +crate://crates.io/getrandom/0.2.3 \
> > +crate://crates.io/itoa/0.4.8 \
> > +crate://crates.io/libc/0.2.109 \
> > +crate://crates.io/memchr/2.4.1 \
> > +crate://crates.io/normalize-line-endings/0.2.2 \
> > +crate://crates.io/num-traits/0.2.14 \
> > +crate://crates.io/ppv-lite86/0.2.15 \
> > +crate://crates.io/predicates-core/0.9.0 \
> > +crate://crates.io/predicates-tree/0.9.0 \
> > +crate://crates.io/predicates/0.9.1 \
> > +crate://crates.io/proc-macro2/1.0.33 \
> > +crate://crates.io/quote/1.0.10 \
> > +crate://crates.io/rand/0.8.4 \
> > +crate://crates.io/rand_core/0.6.3 \
> > +crate://crates.io/rand_chacha/0.3.1 \
> > +crate://crates.io/rand_hc/0.3.1 \
> > +crate://crates.io/redox_syscall/0.2.10 \
> > +crate://crates.io/regex-syntax/0.6.25 \
> > +crate://crates.io/regex/1.5.4 \
> > +crate://crates.io/remove_dir_all/0.5.3 \
> > +crate://crates.io/ryu/1.0.6 \
> > +crate://crates.io/serde/1.0.130 \
> > +crate://crates.io/serde_derive/1.0.130 \
> > +crate://crates.io/serde_json/1.0.72 \
> > +crate://crates.io/syn/1.0.82 \
> > +crate://crates.io/tempfile/3.2.0 \
> > +crate://crates.io/textwrap/0.11.0 \
> > +crate://crates.io/treeline/0.1.0 \
> > +crate://crates.io/unicode-width/0.1.9 \
> > +crate://crates.io/unicode-xid/0.2.2 \
> > +crate://crates.io/wasi/0.10.2+wasi-snapshot-preview1 \
> > +crate://crates.io/winapi-i686-pc-windows-gnu/0.4.0 \
> > +crate://crates.io/winapi-x86_64-pc-windows-gnu/0.4.0 \
> > +crate://crates.io/winapi/0.3.9 \
> > +"
> > +
> > +LIC_FILES_CHKSUM = " \
> > +file://LICENSE;md5=0ffe68749328daf57dd85d5ca6ee981f \
> > +"
> > +
> > +SUMMARY = "An implementation of Android's sparse file format."
> > +HOMEPAGE = "https://gitlab.com/ra_kete/android-sparse-rs;
> > +LICENSE = "MIT"
> > +
> > +BBCLASSEXTEND += "native"
> > --
> > 2.30.2
> >
> >
> > 
> >



--
With best wishes
Dmitry

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177119): 
https://lists.openembedded.org/g/openembedded-core/message/177119
Mute This Topic: https://lists.openembedded.org/mt/96898285/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexandre Belloni via lists.openembedded.org]

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 changed, 2 insertions(+), 2 deletions(-)
>  rename meta/recipes-support/libcap/{libcap_2.66.bb => libcap_2.67.bb} (94%)
> 
> diff --git a/meta/recipes-support/libcap/libcap_2.66.bb 
> b/meta/recipes-support/libcap/libcap_2.67.bb
> similarity index 94%
> rename from meta/recipes-support/libcap/libcap_2.66.bb
> rename to meta/recipes-support/libcap/libcap_2.67.bb
> index c50e9d8cc7..4d4d6d9df1 100644
> --- a/meta/recipes-support/libcap/libcap_2.66.bb
> +++ b/meta/recipes-support/libcap/libcap_2.67.bb
> @@ -7,7 +7,7 @@ HOMEPAGE = "http://sites.google.com/site/fullycapable/;
>  LICENSE = "BSD-3-Clause | GPL-2.0-only"
>  LIC_FILES_CHKSUM_PAM = 
> "file://pam_cap/License;md5=0ad4c9c052b9719ee4fce1bfc7c7dee4"
>  LIC_FILES_CHKSUM = "\
> -file://License;md5=e2370ba375efe9e1a095c26d37e483b8 \
> +file://License;md5=2965a646645b72ecee859b43c592dcaa \

ERROR: libcap-2.67-r0 do_populate_lic: QA Issue: libcap: The LIC_FILES_CHKSUM 
does not match for file://pam_cap/License;md5=0ad4c9c052b9719ee4fce1bfc7c7dee4
ERROR: libcap-2.67-r0 do_populate_lic: Fatal QA errors were found, failing task.

>  ${@bb.utils.contains('PACKAGECONFIG', 'pam', '${LIC_FILES_CHKSUM_PAM}', 
> '', d)} \
>  "
>  
> @@ -20,7 +20,7 @@ SRC_URI = 
> "${KERNELORG_MIRROR}/linux/libs/security/linux-privs/${BPN}2/${BPN}-${
>  SRC_URI:append:class-nativesdk = " \
> 
> file://0001-nativesdk-libcap-Raise-the-size-of-arrays-containing.patch \
> "
> -SRC_URI[sha256sum] = 
> "15c40ededb3003d70a283fe587a36b7d19c8b3b554e33f86129c059a4bb466b2"
> +SRC_URI[sha256sum] = 
> "ce9b22fdc271beb6dae7543da5f74cf24cb82e6848cfd088a5a069dec5ea5198"
>  
>  UPSTREAM_CHECK_URI = 
> "https://www.kernel.org/pub/linux/libs/security/linux-privs/${BPN}2/;
>  
> -- 
> 2.34.1
> 

> 
> 
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177118): 
https://lists.openembedded.org/g/openembedded-core/message/177118
Mute This Topic: https://lists.openembedded.org/mt/96927968/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Stephen Jolley]

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


randy.macl...@windriver.com

27


richard.pur...@linuxfoundation.org

25


ross.bur...@arm.com

23


david.re...@windriver.com

23


bruce.ashfi...@gmail.com

20


jpewhac...@gmail.com

10


pa...@zhukoff.net

7


sakib.sa...@windriver.com

7


saul.w...@windriver.com

6


pi...@toganlabs.com

4


tim.orl...@konsulko.com

4


sundeep.kokko...@gmail.com

3


alexandre.bell...@bootlin.com

2


naveen.go...@windriver.com

2


rybczyn...@gmail.com

2


s...@bigsur.com

2


jon.ma...@arm.com

2


alexis.loth...@bootlin.com

2


jens.ge...@desy.de

1


mathew.pro...@gmail.com

1


sundeep.kokko...@windriver.com

1


mhalst...@linuxfoundation.org

1


yashinde...@gmail.com

1


zheng@windriver.com

1


hongxu@windriver.com

1


louis.ran...@syslinbit.com

1


tvgamb...@gmail.com

1


martin.ja...@gmail.com

1


thomas.per...@bootlin.com

1


Grand Total

216

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177117): 
https://lists.openembedded.org/g/openembedded-core/message/177117
Mute This Topic: https://lists.openembedded.org/mt/96948053/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Stephen Jolley]

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#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 411
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now,  "4.2", "4.3", "4.99" and "Future", the more pressing/urgent
issues being in "4.2" and then "4.3".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177116): 
https://lists.openembedded.org/g/openembedded-core/message/177116
Mute This Topic: https://lists.openembedded.org/mt/96948031/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Carlos Alberto Lopez Perez]

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 neon for aarch64 by default
> 
> Signed-off-by: Markus Volk 
> ---
>  meta/recipes-graphics/graphene/graphene_1.10.8.bb | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-graphics/graphene/graphene_1.10.8.bb 
> b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
> index 813ff74adf..199c460feb 100644
> --- a/meta/recipes-graphics/graphene/graphene_1.10.8.bb
> +++ b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
> @@ -10,8 +10,10 @@ inherit gnomebase gobject-introspection gtk-doc
>  SRC_URI[archive.sha256sum] = 
> "a37bb0e78a419dcbeaa9c7027bcff52f5ec2367c25ec859da31dfde2928f279a"
>  
>  # gtk4 & mutter 41.0 requires graphene build with introspection
> -PACKAGECONFIG ?= "introspection"
> +PACKAGECONFIG ?= "introspection ${@bb.utils.contains('TUNE_FEATURES', 
> 'aarch64', 'neon', '', d)}"
> +
>  PACKAGECONFIG[introspection] = 
> "-Dintrospection=enabled,-Dintrospection=disabled,"
> +PACKAGECONFIG[neon] = "-Darm_neon=true,-Darm_neon=false,"
>  
>  GTKDOC_MESON_OPTION = "gtk_doc"
>  
> 
> 
> 
> 
> 

I think the comment with the link to the upstream bug and the reason for
disabling Neon support should be on the .bb file itself (and not only
the git log).

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177115): 
https://lists.openembedded.org/g/openembedded-core/message/177115
Mute This Topic: https://lists.openembedded.org/mt/96941870/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexandre Belloni via lists.openembedded.org]

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 crash it would be even better.
> > Was this just some some subset of 32 bit arm or all 32 bit arm?
> > 
> > Cheers,
> > 
> > Richard
> 
> Hello Richard,
> 
> I'm not affected by this bug, none of my machines has it but probably  the
> underlying problem is, that there are still issues with neon runtime
> detection and not all arm platforms are guaranteed to have NEON available.
> That said, 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?
> 

Can't we get that out of the tune?


> 
> 
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177114): 
https://lists.openembedded.org/g/openembedded-core/message/177114
Mute This Topic: https://lists.openembedded.org/mt/96893757/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Khem Raj]

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

diff --git 
a/meta/recipes-extended/stress-ng/stress-ng/0001-Include-sys-futex.h-for-clock_adjtime.patch
 
b/meta/recipes-extended/stress-ng/stress-ng/0001-Include-sys-futex.h-for-clock_adjtime.patch
new file mode 100644
index 00..87d2ead46a
--- /dev/null
+++ 
b/meta/recipes-extended/stress-ng/stress-ng/0001-Include-sys-futex.h-for-clock_adjtime.patch
@@ -0,0 +1,32 @@
+From 57f207ec7fb39c8b502f40dbdabd568f6b866a82 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Mon, 13 Feb 2023 12:18:08 -0800
+Subject: [PATCH] Include sys/futex.h for clock_adjtime
+
+Fixes
+core-shim.c:1942:9: error: call to undeclared function 'clock_adjtime'; ISO 
C99 and later do not support implicit function declarations 
[-Wimplicit-function-declaration]
+
+Upstream-Status: Submitted [https://github.com/ColinIanKing/stress-ng/pull/261]
+Signed-off-by: Khem Raj 
+---
+ core-shim.c | 4 
+ 1 file changed, 4 insertions(+)
+
+diff --git a/core-shim.c b/core-shim.c
+index dc539c64..de38e908 100644
+--- a/core-shim.c
 b/core-shim.c
+@@ -66,6 +66,10 @@ UNEXPECTED
+ #include 
+ #endif
+ 
++#if defined(HAVE_SYS_TIMEX_H)
++#include 
++#endif
++
+ #if defined(HAVE_SYS_RANDOM_H)
+ #include 
+ #endif
+-- 
+2.39.1
+
diff --git a/meta/recipes-extended/stress-ng/stress-ng_0.15.03.bb 
b/meta/recipes-extended/stress-ng/stress-ng_0.15.03.bb
index 13a8b49f70..cd7f41a016 100644
--- a/meta/recipes-extended/stress-ng/stress-ng_0.15.03.bb
+++ b/meta/recipes-extended/stress-ng/stress-ng_0.15.03.bb
@@ -7,6 +7,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
 
 SRC_URI = 
"git://github.com/ColinIanKing/stress-ng.git;protocol=https;branch=master \
file://0001-test-float-Make-variables-global.patch \
+   file://0001-Include-sys-futex.h-for-clock_adjtime.patch \
file://0001-Pass-LD_GOLD-1-via-makefile-to-enable-gold-linker.patch"
 SRCREV = "f3be0447c10fd5652b4c3753d56bcaac13fd8917"
 S = "${WORKDIR}/git"
-- 
2.39.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177112): 
https://lists.openembedded.org/g/openembedded-core/message/177112
Mute This Topic: https://lists.openembedded.org/mt/96945922/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Khem Raj]

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-case.patch | 40 +++
 .../gstreamer1.0-plugins-good_1.22.0.bb   |  2 +-
 2 files changed, 41 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good/0001-v4l2-Define-ioctl_req_t-for-posix-linux-case.patch

diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good/0001-v4l2-Define-ioctl_req_t-for-posix-linux-case.patch
 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good/0001-v4l2-Define-ioctl_req_t-for-posix-linux-case.patch
new file mode 100644
index 00..fbbf029a2c
--- /dev/null
+++ 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good/0001-v4l2-Define-ioctl_req_t-for-posix-linux-case.patch
@@ -0,0 +1,40 @@
+From 5ce1e410965ed047a03c09b17796162f0363e396 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Mon, 13 Feb 2023 12:47:31 -0800
+Subject: [PATCH] v4l2: Define ioctl_req_t for posix/linux case
+
+this is an issue seen with musl based linux distros e.g. alpine [1]
+musl is not going to change this since it breaks ABI/API interfaces
+Newer compilers are stringent ( e.g. clang16 ) which can now detect
+signature mismatches in function pointers too, existing code warned but
+did not error with older clang
+
+Fixes
+gstv4l2object.c:544:23: error: incompatible function pointer types assigning 
to 'gint (*)(gint, ioctl_req_t, ...)' (aka 'int (*)(int, unsigned long, ...)') 
from 'int (int, int, ...)' [-Wincompatible-function-pointer-types]
+v4l2object->ioctl = ioctl;
+  ^ ~
+
+[1] https://gitlab.alpinelinux.org/alpine/aports/-/issues/7580
+
+Upstream-Status: Submitted 
[https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/3950]
+Signed-off-by: Khem Raj 
+---
+ sys/v4l2/gstv4l2object.h | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/sys/v4l2/gstv4l2object.h b/sys/v4l2/gstv4l2object.h
+index 3a5c961..4f43008 100644
+--- a/sys/v4l2/gstv4l2object.h
 b/sys/v4l2/gstv4l2object.h
+@@ -76,6 +76,8 @@ typedef gboolean  (*GstV4l2UpdateFpsFunction) (GstV4l2Object 
* v4l2object);
+  * 'unsigned long' for the 2nd parameter */
+ #ifdef __ANDROID__
+ typedef unsigned ioctl_req_t;
++#elif defined(__linux__) && !defined(__GLIBC__) /* musl/linux */
++typedef int ioctl_req_t;
+ #else
+ typedef gulong ioctl_req_t;
+ #endif
+-- 
+2.39.1
+
diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_1.22.0.bb 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_1.22.0.bb
index 85f8a247b1..ef4d82c598 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_1.22.0.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_1.22.0.bb
@@ -6,7 +6,7 @@ BUGTRACKER = 
"https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/issues
 
 SRC_URI = 
"https://gstreamer.freedesktop.org/src/gst-plugins-good/gst-plugins-good-${PV}.tar.xz
 \

file://0001-qt-include-ext-qt-gstqtgl.h-instead-of-gst-gl-gstglf.patch \
-   "
+   file://0001-v4l2-Define-ioctl_req_t-for-posix-linux-case.patch"
 
 SRC_URI[sha256sum] = 
"582e617271e7f314d1a2211e3e3856ae2e4303c8c0d6114e9c4a5ea5719294b0"
 
-- 
2.39.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177113): 
https://lists.openembedded.org/g/openembedded-core/message/177113
Mute This Topic: https://lists.openembedded.org/mt/96945923/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Khem Raj]

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/unfs3/0001-fix-building-on-macOS.patch

diff --git a/meta/recipes-devtools/unfs3/unfs3/0001-fix-building-on-macOS.patch 
b/meta/recipes-devtools/unfs3/unfs3/0001-fix-building-on-macOS.patch
new file mode 100644
index 00..f18ffd3711
--- /dev/null
+++ b/meta/recipes-devtools/unfs3/unfs3/0001-fix-building-on-macOS.patch
@@ -0,0 +1,27 @@
+From 989b87ae46b3183a742031373fbb3e912ab9b666 Mon Sep 17 00:00:00 2001
+From: Andrey Filipenkov 
+Date: Wed, 2 Nov 2022 13:38:40 +0300
+Subject: [PATCH] fix building on macOS
+
+Signed-off-by: Khem Raj 
+Upstream-Status: Backport 
[https://github.com/unfs3/unfs3/commit/989b87ae46b3183a742031373fbb3e912ab9b666]
+---
+ attr.c | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/attr.c b/attr.c
+index 6253e84..0ce9375 100644
+--- a/attr.c
 b/attr.c
+@@ -18,6 +18,8 @@
+ #include 
+ #include 
+ #include 
++#include 
++#include 
+ 
+ #include "backend.h"
+ #include "nfs.h"
+-- 
+2.39.1
+
diff --git a/meta/recipes-devtools/unfs3/unfs3_git.bb 
b/meta/recipes-devtools/unfs3/unfs3_git.bb
index be3870b8a4..9913a503e8 100644
--- a/meta/recipes-devtools/unfs3/unfs3_git.bb
+++ b/meta/recipes-devtools/unfs3/unfs3_git.bb
@@ -16,6 +16,7 @@ SRC_URI = 
"git://github.com/unfs3/unfs3.git;protocol=https;branch=master \

file://0001-daemon.c-Fix-race-window-for-writing-of-the-pid-file.patch \
file://0001-Alias-off64_t-to-off_t-on-linux-if-not-defined.patch \
file://0001-locate.c-Include-attr.h.patch \
+   file://0001-fix-building-on-macOS.patch \
"
 SRCREV = "c8f2d2cd4529955419bad0e163f88d47ff176b8d"
 UPSTREAM_CHECK_GITTAGREGEX = "unfs3\-(?P\d+(\.\d+)+)"
-- 
2.39.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177111): 
https://lists.openembedded.org/g/openembedded-core/message/177111
Mute This Topic: https://lists.openembedded.org/mt/96945921/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Joshua Watt]

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 this:
>
>  "annotations": [
> {
>   "annotationDate": "2023-02-13T19:44:20Z",
>   "annotationType": "OTHER",
>   "annotator": "Tool: oe-spdx-creator - 1.0",
>   "comment": "CUSTOM_VARIABLE=some value or string"
> },
>
> Signed-off-by: Saul Wold 
> ---
>  meta/classes/create-spdx-2.2.bbclass | 7 ++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/create-spdx-2.2.bbclass 
> b/meta/classes/create-spdx-2.2.bbclass
> index f0513af083b..e1bbf646ff9 100644
> --- a/meta/classes/create-spdx-2.2.bbclass
> +++ b/meta/classes/create-spdx-2.2.bbclass
> @@ -30,6 +30,8 @@ SPDX_PRETTY ??= "0"
>
>  SPDX_LICENSES ??= "${COREBASE}/meta/files/spdx-licenses.json"
>
> +SPDX_CUSTOM_ANNOTATION_VARS ??= ""
> +
>  SPDX_ORG ??= "OpenEmbedded ()"
>  SPDX_SUPPLIER ??= "Organization: ${SPDX_ORG}"
>  SPDX_SUPPLIER[doc] = "The SPDX PackageSupplier field for SPDX packages 
> created from \
> @@ -402,7 +404,6 @@ def collect_dep_sources(d, dep_recipes):
>
>  return sources
>
> -
>  python do_create_spdx() {
>  from datetime import datetime, timezone
>  import oe.sbom
> @@ -479,6 +480,10 @@ python do_create_spdx() {
>  if description:
>  recipe.description = description
>
> +if d.getVar("SPDX_CUSTOM_ANNOTATION_VARS"):
> +for var in d.getVar('SPDX_CUSTOM_ANNOTATION_VARS').split():
> +recipe.annotations.append(create_annotation(d, var + "=" + 
> d.getVar(var)))
> +

Seems reasonable. If we need more configuration options, I think we
can add it later with flags, e.g.

 MY_VAR = "foo"
 MY_VAR[spdx-annotator] = "Me!"
 SPDX_CUSTOM_ANNOTATION_VARS = "MY_VAR"

Aslo, in the future if users want package annotations, we can probably do:

 SPDX_CUSTOM_ANNOTATION_VARS:${PN}


>  # Some CVEs may be patched during the build process without incrementing 
> the version number,
>  # so querying for CVEs based on the CPE id can lead to false positives. 
> To account for this,
>  # save the CVEs fixed by patches to source information field in the SPDX.
> --
> 2.25.1
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177110): 
https://lists.openembedded.org/g/openembedded-core/message/177110
Mute This Topic: https://lists.openembedded.org/mt/96944341/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Saul Wold]

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-13T19:44:20Z",
  "annotationType": "OTHER",
  "annotator": "Tool: oe-spdx-creator - 1.0",
  "comment": "CUSTOM_VARIABLE=some value or string"
},

Signed-off-by: Saul Wold 
---
 meta/classes/create-spdx-2.2.bbclass | 7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/meta/classes/create-spdx-2.2.bbclass 
b/meta/classes/create-spdx-2.2.bbclass
index f0513af083b..e1bbf646ff9 100644
--- a/meta/classes/create-spdx-2.2.bbclass
+++ b/meta/classes/create-spdx-2.2.bbclass
@@ -30,6 +30,8 @@ SPDX_PRETTY ??= "0"
 
 SPDX_LICENSES ??= "${COREBASE}/meta/files/spdx-licenses.json"
 
+SPDX_CUSTOM_ANNOTATION_VARS ??= ""
+
 SPDX_ORG ??= "OpenEmbedded ()"
 SPDX_SUPPLIER ??= "Organization: ${SPDX_ORG}"
 SPDX_SUPPLIER[doc] = "The SPDX PackageSupplier field for SPDX packages created 
from \
@@ -402,7 +404,6 @@ def collect_dep_sources(d, dep_recipes):
 
 return sources
 
-
 python do_create_spdx() {
 from datetime import datetime, timezone
 import oe.sbom
@@ -479,6 +480,10 @@ python do_create_spdx() {
 if description:
 recipe.description = description
 
+if d.getVar("SPDX_CUSTOM_ANNOTATION_VARS"):
+for var in d.getVar('SPDX_CUSTOM_ANNOTATION_VARS').split():
+recipe.annotations.append(create_annotation(d, var + "=" + 
d.getVar(var)))
+
 # Some CVEs may be patched during the build process without incrementing 
the version number,
 # so querying for CVEs based on the CPE id can lead to false positives. To 
account for this,
 # save the CVEs fixed by patches to source information field in the SPDX.
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177109): 
https://lists.openembedded.org/g/openembedded-core/message/177109
Mute This Topic: https://lists.openembedded.org/mt/96944341/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Markus Volk]

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



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177108): 
https://lists.openembedded.org/g/openembedded-core/message/177108
Mute This Topic: https://lists.openembedded.org/mt/96933955/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Markus Volk]

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: 



?


sure


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177107): 
https://lists.openembedded.org/g/openembedded-core/message/177107
Mute This Topic: https://lists.openembedded.org/mt/96933955/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Markus Volk]

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 Volk 
---
 meta/recipes-graphics/graphene/graphene_1.10.8.bb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-graphics/graphene/graphene_1.10.8.bb 
b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
index 813ff74adf..199c460feb 100644
--- a/meta/recipes-graphics/graphene/graphene_1.10.8.bb
+++ b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
@@ -10,8 +10,10 @@ inherit gnomebase gobject-introspection gtk-doc
 SRC_URI[archive.sha256sum] = 
"a37bb0e78a419dcbeaa9c7027bcff52f5ec2367c25ec859da31dfde2928f279a"
 
 # gtk4 & mutter 41.0 requires graphene build with introspection
-PACKAGECONFIG ?= "introspection"
+PACKAGECONFIG ?= "introspection ${@bb.utils.contains('TUNE_FEATURES', 
'aarch64', 'neon', '', d)}"
+
 PACKAGECONFIG[introspection] = 
"-Dintrospection=enabled,-Dintrospection=disabled,"
+PACKAGECONFIG[neon] = "-Darm_neon=true,-Darm_neon=false,"
 
 GTKDOC_MESON_OPTION = "gtk_doc"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177106): 
https://lists.openembedded.org/g/openembedded-core/message/177106
Mute This Topic: https://lists.openembedded.org/mt/96941870/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Ahmad Fatoum]

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 included from 
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/barebox-2023.01.0/scripts/kwboot-target.c:1:
> | 
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/barebox-2023.01.0/scripts/kwboot.c:
>  In function 'kwboot_tty_recv':
> | 
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/barebox-2023.01.0/scripts/kwboot.c:141:9:
>  error: unknown type name 'fd_set'
> |   141 | fd_set rfds;
> |   | ^~
> | 
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/barebox-2023.01.0/scripts/kwboot.c:142:24:
>  error: storage size of 'tv' isn't known
> |   142 | struct timeval tv;
> |   |^~
> | 
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/barebox-2023.01.0/scripts/kwboot.c:147:9:
>  warning: implicit declaration of function 'FD_ZERO' 
> [-Wimplicit-function-declaration]
> |   147 | FD_ZERO();
> |   | ^~~
> | 
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/barebox-2023.01.0/scripts/kwboot.c:148:9:
>  warning: implicit declaration of function 'FD_SET'; did you mean 'L_SET'? 
> [-Wimplicit-function-declaration]
> |   148 | FD_SET(fd, );
> |   | ^~
> |   | L_SET
> | 
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/barebox-2023.01.0/scripts/kwboot.c:157:24:
>  warning: implicit declaration of function 'select' 
> [-Wimplicit-function-declaration]
> |   157 | nfds = select(fd + 1, , NULL, NULL, );
> |   |^~
> | 
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/barebox-2023.01.0/scripts/kwboot.c:142:24:
>  warning: unused variable 'tv' [-Wunused-variable]
> |   142 | struct timeval tv;
> |   |^~
> | 
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/barebox-2023.01.0/scripts/kwboot.c:
>  In function 'kwboot_terminal':
> | 
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/barebox-2023.01.0/scripts/kwboot.c:571:17:
>  error: unknown type name 'fd_set'
> |   571 | fd_set rfds;
> |   | ^~
> | 
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/barebox-2023.01.0/scripts/kwboot.c:586:21:
>  warning: implicit declaration of function 'FD_ISSET' 
> [-Wimplicit-function-declaration]
> |   586 | if (FD_ISSET(tty, )) {
> |   | ^~~~
> | make[2]: *** [scripts/Makefile.userprogs:28: scripts/kwboot-target] Error 1
> | ERROR: oe_runmake failed
> | make[1]: Leaving directory 
> '/home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/build'
> | make: Leaving directory 
> '/home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/barebox-2023.01.0'
> | WARNING: 
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/temp/run.do_compile.3586889:170
>  exit 1 from 'exit 1'
> | WARNING: Backtrace (BB generated script):
> | make[1]: *** 
> [/home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/barebox-2023.01.0/Makefile:976:
>  scripts] Error 2
> | make: *** [Makefile:180: sub-make] Error 2
> | #1: bbfatal_log, 
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/temp/run.do_compile.3586889,
>  line 170
> | #2: die, 
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/temp/run.do_compile.3586889,
>  line 154
> | #3: oe_runmake, 
> /home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/work/core2-64-poky-linux-musl/barebox-tools/2023.01.0-r0/temp/run.do_compile.3586889,
>  line 149
> | #4: do_compile, 
> 

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

[Bastian Krause]

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 
---
  meta/recipes-graphics/graphene/graphene_1.10.8.bb | 4 +++-
  1 file changed, 3 insertions(+), 1 deletion(-)


0e0849cd1 ("graphene: disable neon support on arm 32bits") from meta-oe
needs to be reverted to make this patch work, right?

Regards,
Bastian



diff --git a/meta/recipes-graphics/graphene/graphene_1.10.8.bb 
b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
index 813ff74adf..199c460feb 100644
--- a/meta/recipes-graphics/graphene/graphene_1.10.8.bb
+++ b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
@@ -10,8 +10,10 @@ inherit gnomebase gobject-introspection gtk-doc
  SRC_URI[archive.sha256sum] = 
"a37bb0e78a419dcbeaa9c7027bcff52f5ec2367c25ec859da31dfde2928f279a"
  
  # gtk4 & mutter 41.0 requires graphene build with introspection

-PACKAGECONFIG ?= "introspection"
+PACKAGECONFIG ?= "introspection ${@bb.utils.contains('TUNE_FEATURES', 'aarch64', 
'neon', '', d)}"
+
  PACKAGECONFIG[introspection] = 
"-Dintrospection=enabled,-Dintrospection=disabled,"
+PACKAGECONFIG[neon] = "-Darm_neon=true,-Darm_neon=false,"
  
  GTKDOC_MESON_OPTION = "gtk_doc"


--
Pengutronix e.K.   | |
Steuerwalder Str. 21   | http://www.pengutronix.de/  |
31137 Hildesheim, Germany  | Phone: +49-5121-206917-0|
Amtsgericht Hildesheim, HRA 2686   | Fax:   +49-5121-206917- |


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177104): 
https://lists.openembedded.org/g/openembedded-core/message/177104
Mute This Topic: https://lists.openembedded.org/mt/96933955/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Carlos Alberto Lopez Perez]

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 Volk 
> ---
>  meta/recipes-graphics/graphene/graphene_1.10.8.bb | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-graphics/graphene/graphene_1.10.8.bb 
> b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
> index 813ff74adf..199c460feb 100644
> --- a/meta/recipes-graphics/graphene/graphene_1.10.8.bb
> +++ b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
> @@ -10,8 +10,10 @@ inherit gnomebase gobject-introspection gtk-doc
>  SRC_URI[archive.sha256sum] = 
> "a37bb0e78a419dcbeaa9c7027bcff52f5ec2367c25ec859da31dfde2928f279a"
>  
>  # gtk4 & mutter 41.0 requires graphene build with introspection
> -PACKAGECONFIG ?= "introspection"
> +PACKAGECONFIG ?= "introspection ${@bb.utils.contains('TUNE_FEATURES', 
> 'aarch64', 'neon', '', d)}"
> +
>  PACKAGECONFIG[introspection] = 
> "-Dintrospection=enabled,-Dintrospection=disabled,"
> +PACKAGECONFIG[neon] = "-Darm_neon=true,-Darm_neon=false,"
>  
>  GTKDOC_MESON_OPTION = "gtk_doc"
>  
> 
> 

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: https://github.com/ebassi/graphene/issues/215

?

That way anyone can known in the future why that was disabled for ARM-32
and check if the upstream issue got fixed in order to enable it back by
default.

There is a related discussion at:
https://github.com/Igalia/meta-webkit/pull/448

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177103): 
https://lists.openembedded.org/g/openembedded-core/message/177103
Mute This Topic: https://lists.openembedded.org/mt/96933955/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[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 neon for aarch64 by default

Signed-off-by: Markus Volk 
---
 meta/recipes-graphics/graphene/graphene_1.10.8.bb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-graphics/graphene/graphene_1.10.8.bb 
b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
index 813ff74adf..199c460feb 100644
--- a/meta/recipes-graphics/graphene/graphene_1.10.8.bb
+++ b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
@@ -10,8 +10,10 @@ inherit gnomebase gobject-introspection gtk-doc
 SRC_URI[archive.sha256sum] = 
"a37bb0e78a419dcbeaa9c7027bcff52f5ec2367c25ec859da31dfde2928f279a"
 
 # gtk4 & mutter 41.0 requires graphene build with introspection
-PACKAGECONFIG ?= "introspection"
+PACKAGECONFIG ?= "introspection ${@bb.utils.contains('TUNE_FEATURES', 
'aarch64', 'neon', '', d)}"
+
 PACKAGECONFIG[introspection] = 
"-Dintrospection=enabled,-Dintrospection=disabled,"
+PACKAGECONFIG[neon] = "-Darm_neon=true,-Darm_neon=false,"
 
 GTKDOC_MESON_OPTION = "gtk_doc"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177102): 
https://lists.openembedded.org/g/openembedded-core/message/177102
Mute This Topic: https://lists.openembedded.org/mt/96933955/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexander Kanavin]

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 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:
> PACKAGECONFIG ?= "introspection ${@bb.utils.contains('TUNE_FEATURES', 
> 'aarch64', 'neon', '', d)}"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177101): 
https://lists.openembedded.org/g/openembedded-core/message/177101
Mute This Topic: https://lists.openembedded.org/mt/96933147/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Markus Volk]

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:
PACKAGECONFIG ?= "introspection ${@bb.utils.contains('TUNE_FEATURES', 
'aarch64', 'neon', '', d)}"



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177100): 
https://lists.openembedded.org/g/openembedded-core/message/177100
Mute This Topic: https://lists.openembedded.org/mt/96933147/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexander Kanavin]

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  wrote:
>
> 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 (#177099): 
https://lists.openembedded.org/g/openembedded-core/message/177099
Mute This Topic: https://lists.openembedded.org/mt/96933147/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Markus Volk]

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 (#177098): 
https://lists.openembedded.org/g/openembedded-core/message/177098
Mute This Topic: https://lists.openembedded.org/mt/96933147/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Markus Volk]

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? Since oe-core should be kept 
free of :append, just remove the '?'.



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177097): 
https://lists.openembedded.org/g/openembedded-core/message/177097
Mute This Topic: https://lists.openembedded.org/mt/96933147/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexander Kanavin]

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 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.8.bb | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-graphics/graphene/graphene_1.10.8.bb 
> b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
> index 813ff74adf..0efe6520d8 100644
> --- a/meta/recipes-graphics/graphene/graphene_1.10.8.bb
> +++ b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
> @@ -11,7 +11,9 @@ SRC_URI[archive.sha256sum] = 
> "a37bb0e78a419dcbeaa9c7027bcff52f5ec2367c25ec859da3
>
>  # gtk4 & mutter 41.0 requires graphene build with introspection
>  PACKAGECONFIG ?= "introspection"
> +PACKAGECONFIG:aarch64 += "neon"
>  PACKAGECONFIG[introspection] = 
> "-Dintrospection=enabled,-Dintrospection=disabled,"
> +PACKAGECONFIG[neon] = "-Darm_neon=true,-Darm_neon=false,"
>
>  GTKDOC_MESON_OPTION = "gtk_doc"
>
> --
> 2.34.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177096): 
https://lists.openembedded.org/g/openembedded-core/message/177096
Mute This Topic: https://lists.openembedded.org/mt/96933147/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Markus Volk]

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/openembedded-core/message/177095
Mute This Topic: https://lists.openembedded.org/mt/96933123/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexander Kanavin]

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. 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.8.bb | 2 ++ 1 file changed, 2 
> insertions(+) diff --git a/meta/recipes-graphics/graphene/graphene_1.10.8.bb 
> b/meta/recipes-graphics/graphene/graphene_1.10.8.bb index 
> 813ff74adf..f32112118f 100644 --- 
> a/meta/recipes-graphics/graphene/graphene_1.10.8.bb +++ 
> b/meta/recipes-graphics/graphene/graphene_1.10.8.bb @@ -11,7 +11,9 @@ 
> SRC_URI[archive.sha256sum] = 
> "a37bb0e78a419dcbeaa9c7027bcff52f5ec2367c25ec859da3 # gtk4 & mutter 41.0 
> requires graphene build with introspection PACKAGECONFIG ?= "introspection" 
> +#PACKAGECONFIG:aarch64 += "neon" PACKAGECONFIG[introspection] = 
> "-Dintrospection=enabled,-Dintrospection=disabled," +PACKAGECONFIG[neon] = 
> "-Darm_neon=true,-Darm_neon=false," GTKDOC_MESON_OPTION = "gtk_doc"
> --
> 2.34.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177094): 
https://lists.openembedded.org/g/openembedded-core/message/177094
Mute This Topic: https://lists.openembedded.org/mt/96933123/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[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 neon for aarch64 by default

Signed-off-by: Markus Volk 
---
 meta/recipes-graphics/graphene/graphene_1.10.8.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-graphics/graphene/graphene_1.10.8.bb 
b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
index 813ff74adf..0efe6520d8 100644
--- a/meta/recipes-graphics/graphene/graphene_1.10.8.bb
+++ b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
@@ -11,7 +11,9 @@ SRC_URI[archive.sha256sum] = 
"a37bb0e78a419dcbeaa9c7027bcff52f5ec2367c25ec859da3
 
 # gtk4 & mutter 41.0 requires graphene build with introspection
 PACKAGECONFIG ?= "introspection"
+PACKAGECONFIG:aarch64 += "neon"
 PACKAGECONFIG[introspection] = 
"-Dintrospection=enabled,-Dintrospection=disabled,"
+PACKAGECONFIG[neon] = "-Darm_neon=true,-Darm_neon=false,"
 
 GTKDOC_MESON_OPTION = "gtk_doc"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177093): 
https://lists.openembedded.org/g/openembedded-core/message/177093
Mute This Topic: https://lists.openembedded.org/mt/96933147/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Markus Volk]

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 neon for aarch64 by default

Signed-off-by: Markus Volk >

---
 meta/recipes-graphics/graphene/graphene_1.10.8.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-graphics/graphene/graphene_1.10.8.bb 
b/meta/recipes-graphics/graphene/graphene_1.10.8.bb

index 813ff74adf..f32112118f 100644
--- a/meta/recipes-graphics/graphene/graphene_1.10.8.bb
+++ b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
@@ -11,7 +11,9 @@ SRC_URI[archive.sha256sum] = 
"a37bb0e78a419dcbeaa9c7027bcff52f5ec2367c25ec859da3


 # gtk4 & mutter 41.0 requires graphene build with introspection
 PACKAGECONFIG ?= "introspection"
+#PACKAGECONFIG:aarch64 += "neon"
 PACKAGECONFIG[introspection] = 
"-Dintrospection=enabled,-Dintrospection=disabled,"

+PACKAGECONFIG[neon] = "-Darm_neon=true,-Darm_neon=false,"

 GTKDOC_MESON_OPTION = "gtk_doc"

--
2.34.1




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177092): 
https://lists.openembedded.org/g/openembedded-core/message/177092
Mute This Topic: https://lists.openembedded.org/mt/96933123/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[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 neon for aarch64 by default

Signed-off-by: Markus Volk 
---
 meta/recipes-graphics/graphene/graphene_1.10.8.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-graphics/graphene/graphene_1.10.8.bb 
b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
index 813ff74adf..f32112118f 100644
--- a/meta/recipes-graphics/graphene/graphene_1.10.8.bb
+++ b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
@@ -11,7 +11,9 @@ SRC_URI[archive.sha256sum] = 
"a37bb0e78a419dcbeaa9c7027bcff52f5ec2367c25ec859da3
 
 # gtk4 & mutter 41.0 requires graphene build with introspection
 PACKAGECONFIG ?= "introspection"
+#PACKAGECONFIG:aarch64 += "neon"
 PACKAGECONFIG[introspection] = 
"-Dintrospection=enabled,-Dintrospection=disabled,"
+PACKAGECONFIG[neon] = "-Darm_neon=true,-Darm_neon=false,"
 
 GTKDOC_MESON_OPTION = "gtk_doc"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177091): 
https://lists.openembedded.org/g/openembedded-core/message/177091
Mute This Topic: https://lists.openembedded.org/mt/96933123/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Markus Volk]

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://lists.openembedded.org/g/openembedded-core/message/177090
Mute This Topic: https://lists.openembedded.org/mt/96893757/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

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

Signed-off-by: Markus Volk 
---
 meta/recipes-graphics/graphene/graphene_1.10.8.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-graphics/graphene/graphene_1.10.8.bb 
b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
index 813ff74adf..4f1a0047fd 100644
--- a/meta/recipes-graphics/graphene/graphene_1.10.8.bb
+++ b/meta/recipes-graphics/graphene/graphene_1.10.8.bb
@@ -12,6 +12,7 @@ SRC_URI[archive.sha256sum] = 
"a37bb0e78a419dcbeaa9c7027bcff52f5ec2367c25ec859da3
 # gtk4 & mutter 41.0 requires graphene build with introspection
 PACKAGECONFIG ?= "introspection"
 PACKAGECONFIG[introspection] = 
"-Dintrospection=enabled,-Dintrospection=disabled,"
+PACKAGECONFIG[neon] = "-Darm_neon=true,-Darm_neon=false,"
 
 GTKDOC_MESON_OPTION = "gtk_doc"
 
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177089): 
https://lists.openembedded.org/g/openembedded-core/message/177089
Mute This Topic: https://lists.openembedded.org/mt/96932933/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[BINDU]

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 Thakur 
---
 meta/recipes-devtools/git/git.inc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-devtools/git/git.inc 
b/meta/recipes-devtools/git/git.inc
index b5d0004712..9cc4092e17 100644
--- a/meta/recipes-devtools/git/git.inc
+++ b/meta/recipes-devtools/git/git.inc
@@ -24,6 +24,9 @@ CVE_PRODUCT = "git-scm:git"
 # we don't see this as a major issue for our general users/usecases.
 CVE_CHECK_WHITELIST += "CVE-2022-24975"
 
+# This is specific to Git-for-Windows
+CVE_CHECK_WHITELIST += "CVE-2022-41953"
+
 PACKAGECONFIG ??= ""
 PACKAGECONFIG[cvsserver] = ""
 PACKAGECONFIG[svn] = ""
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177088): 
https://lists.openembedded.org/g/openembedded-core/message/177088
Mute This Topic: https://lists.openembedded.org/mt/96932800/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Markus Volk]

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 of 32 bit arm or all 32 bit arm?

Cheers,

Richard


Hello Richard,

I'm not affected by this bug, none of my machines has it but probably  
the underlying problem is, that there are still issues with neon 
runtime detection and not all arm platforms are guaranteed to have NEON 
available. That said, 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 (#177087): 
https://lists.openembedded.org/g/openembedded-core/message/177087
Mute This Topic: https://lists.openembedded.org/mt/96893757/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-