linux-yoto/6.12: bsp/arm: fix CONFIG_CRYPTO_LIB_CHACHA
A message that is not in the archive (sent off-list or not yet received): [email protected]
Ooops. I see the "yoto" now.
I can send a v2, or if you want to tweak it on the way in. Either is fine with me.
Bruce
Quoted 119 lines · Bruce Ashfield via lists.openembedded.org
From: Bruce Ashfield <[email protected]>
Integrating the following commit(s) to linux-yocto/.:
1/2 [
Author: Mikko Rapeli
Email: [email protected]
Subject: genericarm64: addCONFIG_CRYPTO_LIB_CHACHA=m
Date: Wed, 7 May 2025 14:43:40 +0300Fixes
CONFIG_CRYPTO_CHACHA20_NEONbuild as module:WARNING: [kernel config]: specified values did not make it into the
kernel's final configuration:[NOTE]: '
CONFIG_CRYPTO_CHACHA20_NEON' last val (m) and .config val
(n) do not match
[INFO]:CONFIG_CRYPTO_CHACHA20_NEON: nSigned-off-by Mikko Rapeli <[email protected]>Signed-off-by Bruce Ashfield <[email protected]>]
2/2 [
Author: Mikko Rapeli
Email: [email protected]
Subject: qemuarma15.cfg: enableCONFIG_CRYPTO_LIB_CHACHA
Date: Wed, 7 May 2025 14:43:41 +0300It's a dependency of
CONFIG_CRYPTO_CHACHA20_NEON. Fixes:[NOTE]: '
CONFIG_CRYPTO_CHACHA20_NEON' last val (y) and .config val
(n) do not match
[INFO]:CONFIG_CRYPTO_CHACHA20_NEON: nSigned-off-by Mikko Rapeli <[email protected]>Signed-off-by Bruce Ashfield <[email protected]>]
Signed-off-by Bruce Ashfield <[email protected]>---
Apply this on top of my recent kernel series and the warnings should be gone from the various arm builds.
Bruce
meta/recipes-kernel/linux/linux-yocto-rt_6.12.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-tiny_6.12.bb | 2 +- meta/recipes-kernel/linux/linux-yocto_6.12.bb | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)meta/recipes-kernel/linux/linux-yocto-rt_6.12.bb +1
-1@@ -15,7 +15,7 @@ python () { } SRCREV_machine ?= "28fcf1f308c59515410f6a0d0bc3278d5296a3c1" -SRCREV_meta ?= "23e01a412ce53c2b1a9ac83d143702c7d03ec0f0" +SRCREV_meta ?= "a50ff542f8d79235030741f9e850d34768907d2d" SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine;protocol=https
<http://git.yoctoproject.org/linux-yocto.git;branch=$%7BKBRANCH%7D;name=machine;protocol=https>\ git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-6.12;destsuffix=${KMETA};protocol=https
<http://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-6.12;destsuffix=$%7BKMETA%7D;protocol=https>
"meta/recipes-kernel/linux/linux-yocto-tiny_6.12.bb +1
-1@@ -18,7 +18,7 @@ KMETA = "kernel-meta" KCONF_BSP_AUDIT_LEVEL = "2" SRCREV_machine ?= "5b22e7aef539a991b75fa45101cbc02051327cb6" -SRCREV_meta ?= "23e01a412ce53c2b1a9ac83d143702c7d03ec0f0" +SRCREV_meta ?= "a50ff542f8d79235030741f9e850d34768907d2d" PV = "${LINUX_VERSION}+git"meta/recipes-kernel/linux/linux-yocto_6.12.bb +0
-0@@ -29,7 +29,7 @@ SRCREV_machine:qemux86 ?="
5b22e7aef539a991b75fa45101cbc02051327cb6"
SRCREV_machine:qemux86-64 ?= "5b22e7aef539a991b75fa45101cbc02051327cb6" SRCREV_machine:qemumips64 ?= "8e88d1714f7f56efc4650cf84b86845d44c01eb1"SRCREV_machine?= "5b22e7aef539a991b75fa45101cbc02051327cb6"meta/recipes-kernel/linux/linux-yocto_6.12.bb +1
-1-SRCREV_meta ?= "23e01a412ce53c2b1a9ac83d143702c7d03ec0f0" +SRCREV_meta ?= "a50ff542f8d79235030741f9e850d34768907d2d" # set your preferred provider of linux-yocto to 'linux-yocto-upstream',and you'll
# get the <version>/base branch, which is pure upstream -stable, and the same -- 2.39.2-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#216119):
https://lists.openembedded.org/g/openembedded-core/message/216119
Mute This Topic: https://lists.openembedded.org/mt/112669991/1050810
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Signature · 3 lines
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
Quoted 4 lines · Bruce Ashfield
Ooops. I see the "yoto" now.
I can send a v2, or if you want to tweak it on the way in. Either is fine with me.
I can tweak, thanks. I'll put this in for testing overnight.
Cheers,
Richard