Date   

Yocto Technical Team Minutes, Engineering Sync, for June 8, 2021

Trevor Woerner
 

Yocto Technical Team Minutes, Engineering Sync, for June 8, 2021
archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit

== disclaimer ==
Best efforts are made to ensure the below is accurate and valid. However,
errors sometimes happen. If any errors or omissions are found, please feel
free to reply to this email with any corrections.

== attendees ==
Trevor Woerner, Stephen Jolley, Armin Kuster, Steve Sakoman, Tony
Tascioglu, Peter Kjellerstedt, Saul Wold, Bruce Ashfield, Jon Mason,
Richard Purdie, Michael Halstead, Joshua Watt, Jan-Simon Möller, Randy
MacLeod, Tim Orling, angolini, Ross Burton, sakib.sajal@WR

== notes ==
- 3.4 m1 due to build this week (honister)
- 3.1.8 released (dunfell)
- possible AB-INT cause identified (aufs patches in linux-yocto) 3.4 m1 to be
held pending
- another AB-INT caused by kernel upgrade on centos8, also affects 3.4 m1
- existing multiconfig patches seem to fix some things but break others;
multiconfig needs simpler test cases
- record high levels of AB-INT issues

== general ==
RP: what to do about the AB-INT blockers?


Bruce: i’m preparing a new check of aufs to see if i can find any
problematic issues. we also saw things with 5.12 as well, which has
completely different code in aufs, so i’m not 100% sure we’ve found
the problem. but i’m preparing a new series which we can submit for
testing to see where it goes
RP: the centos8 issues causes any build to have failures. this is an
intermittent issue, so it’s not easy to pin down to specific things,
just educated guessing. ideally we’d not be blocking m1
Bruce: 5.12 is no longer the shiny new thing, so i’ll be bringing in 5.13
soon-ish. so i question blocking m1
RP: something is destabilizing the AB, but the AB is more stable when using
base rather than standard/base
Bruce: i could revert the aufs thing so we can move forward with m1
RP: my priority is to stabilize the AB
Bruce: it appears that there are upstream problems with the -stable backports
(specifically we’ve seen a partial preempt_rt backport patch) so there
are issues all around. for example the aufs maintainer maintains his own
per-release branches for patches which we pull in, but it’s possible
there are problems there
RP: this is not the only thing blocking m1 (we’re not stuck waiting for you)
but hopefully it gets resolved by the time the other problem is fixed
RP: there’s also an lttng issue which I’ve sent


RP: centos8
MichaelH: there is a script that Khem gave us and AlexK was looking at running
it to find out the problem. we needed to install more packages to get the
script working. other options are to run a different kernel on centos8
machines (instead of the default)
RP: is there much risk in downgrading the kernel back to before the last
maintenance?
MichaelH: no
RP: we have 2 centos8 workers. let’s downgrade the kernel on one and leave
the other as-is so we can test against both setups. that way both machines
will be running a RedHat kernel, one will just be older
MichaelH: there were other things updated last friday other than the kernel,
so the issue could be something else (it was a BIG update)
RP: it looked like a syscall problem, so let’s start there and consider
other things if that doesn’t solve the issue


PeterK: tagging (from last week)
MichaelH: we decided prior to 3.3 to use old style, and new yocto version
number and branch name tag in 3.4 (honister) and after
RP: dunfell remains unchanged, hardknott tweaked slightly


Randy: i don’t see any reports, so whoever is running swat…
Randy: valgrind updates
Randy: progress on make-job-server, cmake based builds are interfering
RP: qemuarm building is failing with valgrind issues in ptest
Randy: arm? or arm64?
RP: arm64, we only test arm64 in ptest
Randy: if make-job-server works we’ll need to do something similar for ninja
RP: if you have a patch that controls make and cmake then that’s a start.
i’d like to get that into the infrastructure with just that
Randy: np


Randy: do we have an understanding of how busy machines are? is the AB busy on
weekends?
RP: i usually schedule things in my nights. on weekends regular builds are
turned into full builds. on top of that you have builds from AlexK, kernel
builds from Bruce, and dunfell builds from Steve. we can’t run it 100%
because it does need “healing time”


JPEW: i’ve been looking at SBOM
Ross: i’m curious
JPEW: started with meta-doubleopen, generates mostly valid SBOM, submitted a
couple patches so they would pass the validator. i think we’re sending
someone to the plugfest. the layer needs some cleanup work, some of it
would integrate better into the core. the SBOMs are *HUGE*, 500MB for
core-image-minimal (!!)
RP: we don’t have to do this for SBOM, so for core i think we only need to
look at more basic functionality. i like the feature of examining the
final binaries and working backwards to figuring out which source files
were part of the build, but that could be somewhere outside the SBOM
JPEW: i looked at some of the license mapping things
RP: isn’t there already a function that does that
JPEW: looked but didn’t find
RP: i think it’s spread all over and should be consolidated into a separate
function
JPEW: generate the different components with different tasks for a given
recipe. they create a “package” for the recipe itself, but then
“package” for each package generated by the build. so you end up
with n+1 packages for each recipe, then you need to define all the
relationships, so there are multiple tasks fiddling with one SPDX file
RP: why not just one
JPEW: 1. there’s a recipe identifier step (which is separate than actually
generating SPDXes) 2. package post function for produced packages 3. runs
after 1 and 2 and replicates what the archiver is doing (figures out what
files went into recipe) and mostly does the relationships
JPEW: not everything has a packaging step so there’s a step that has to be
done at the very end to make sure everything in the image has
been accounted for
RP: if there’s no do-package then it’s not going into the image
Ross: we have pieces of firmware that just drop things into deploy
RP: there are 3 ways to get something into the image: 1. packages 2. do deploy
3. images
JPEW: we could have an image in an image, so we’d need this post step anyway
RP: how do we produce the SPDX file and pull it into the image
JPEW: it gets complicated
RP: can we supplement package data with extra things? we could put more data
into packagedata which could make some of these other things easier
JPEW: this could get rid of the post-processing step. they were tripping over
a number of things that could be made easier to having the metadata setup
with this information (expecting to do SBOMs)
JPEW: we can’t know the package data post mortem
RP: there is a call we can make, then all this info is correct again
JPEW: ah! that would help it not be spread across these 3 tasks
TimO: reminds me of what i was encountering while doing the perl-dep work
earlier. the problem i found is that i could only see the files if i was
just building them, i wouldn’t see them when pulling from sstate
RP: there’s 2 directories: 1 package data for currently building thing 2.
package data for all its predecessors. you’re probably interested in 2,
but are looking in 1


TimO: played with Ross’s maynard branch. gives you a gnome desktop on
weston. but has AGL stuff in it and future support is unknown.
TimO: so i don’t see any strong contenders. i don’t think we want sway or
wrlroots. i don’t think ivi shell is what we want
JPEW: no because everything has to be written in ivi-shell
TimO: that’s what i thought
JPEW: phosh, but dependencies
TimO: this would require lots of stuff brought into core, which is
questionable and i don’t want to maintain any of our own forks
JPEW: i agree
TimO: i think AGL is going to be looking at flutter, but i don’t think that
makes sense for us
J-S: yes, there is some traction to running flutter, but not sure if that’s
a good fit for us. ideal is to run something purely upstream
RP: i think we should just maintain the status-quo a bit longer to see if the
dust settles. there’s lot’s of churn out there
TimO: even if we were even able to port matchbox to weston, would we even want
that as a reference desktop?
Ross: *if* it were maintained, then a maintained solution would be better
than an unmaintained on. but if we have to maintain it ourselves then the
decision is not as easy
RP: matchbox is good on small screens
TimO: most lightweight stuff i know is x11-based
Ross: matchbox isn’t the prettiest, but it is good for what it does
JPEW: phones and tablets
TimO: phones, tables, and kiosks
RP: how big is the gnome stuff
Ross: quite big
JPEW: lots of silly dependencies in phosh, e.g. lots of jSON descriptions for
mutter things even if you’re not running mutter on the target. so this
ends up pulling gnome desktop and lots of gtkwebkit things
RP: but we already have gtkwebkit in core, and the silly dependencies seem
fixable. Ross have you looked at phosh?
Ross: no
JPEW: gnome desktop 3, network manager, pollkit-systemd, gnome shell g
settings
RP: systemd dependency. does it work?
JPEW: it builds but the graphics didn’t come up. i think librsvg is too old
RP: i think our librsvg stuff is broken because of rust


Re: Managing chinese text input

Masahiko Kimoto
 

Hi Maruo,

Fcitx recipes are provided as meta-inputmethod from Clear-Code Inc.

https://gitlab.com/clear-code/meta-inputmethod

In addition, we, Cybertrust Japan, have recipes of fcitx-chewing,
fcitx-hangul and fcitx-m17n.

However, we need several company internal processes to contribute them
to public.

Would you have time to wait for them?

From: "Mauro Ziliani" <mauro@faresoftware.it>
Subject: [yocto] Managing chinese text input
Date: Tue, 8 Jun 2021 15:17:43 +0200

> Hi all.
> I'm coding my own keyboard for a touch screen device based on Qt/Qml 5.6.
> I'd like to implement a chinese input method.
> The keyboard is embedded in the software and it is activated only inside the software.
>
> The system is based on an old mix of Jethro/Krogoth
> I know there ibus framework for this, but it is not included in yocto bsp.
> Any idea about?
> Best regards,
> MZ
>
> Sent from Mailspring (https://getmailspring.com/), the best free email app for work

----------------------------------------------------------------------
木本 雅彦 / Masahiko Kimoto, Ph.D.
E-mail: kimoto@ohnolab.org URL: http://www.ohnolab.org/~kimoto


Re: [meta-zephyr][PATCHv2 1/5] zephyr-kernel: Clone mbedtls

Naveen Saini
 

Made few changes in this patch. Re-sent patchset including some additional patches.

Regards,
Naveen

-----Original Message-----
From: Amit Kucheria <amit.kucheria.ext@huawei.com>
Sent: Tuesday, June 8, 2021 7:11 PM
To: Saini, Naveen Kumar <naveen.kumar.saini@intel.com>;
amit.kucheria@verdurent.com; yocto@lists.yoctoproject.org; Wojciech
Zmuda <wojciech.zmuda@huawei.com>; Andrei Gherzan
<andrei.gherzan@huawei.com>
Subject: RE: [meta-zephyr][PATCHv2 1/5] zephyr-kernel: Clone mbedtls

Hi Naveen,

I'll take a look with the specific revision ID mentioned. I don't see a build
failure here locally.

On a related note, since 2.6 is now released, should we just focus on getting
all this working on 2.6 (assuming you'll move meta-zephyr to it soon)?

Regards,
Amit

-----Original Message-----
From: Saini, Naveen Kumar [mailto:naveen.kumar.saini@intel.com]
Sent: 08 June 2021 16:10
To: amit.kucheria@verdurent.com; yocto@lists.yoctoproject.org;
Wojciech Zmuda <wojciech.zmuda@huawei.com>; Andrei Gherzan
<andrei.gherzan@huawei.com>
Cc: Amit Kucheria <amit.kucheria.ext@huawei.com>
Subject: RE: [meta-zephyr][PATCHv2 1/5] zephyr-kernel: Clone mbedtls

Build failing:

Could not open 'poky/build-zephyr/tmp-newlib/work/armv7m-yocto-
eabi/zephyr-mqtt-publisher/2.5.0+gitAUTOINC+fe7c2efca8_c3bd2094f9-
r0/git/' (in 'osource "$(ZEPHYR_MBEDTLS_KCONFIG)"') (EISDIR: Is a
directory)



To fix, can you try following revision for mbedtls.
- name: mbedtls
revision: 24d84ecff195fb15c889d9046e44e4804d626c67
https://github.com/zephyrproject-rtos/zephyr/blob/zephyr-
v2.5.0/west.yml#L94

Regards,
Naveen



-----Original Message-----
From: amit.kucheria@verdurent.com <amit.kucheria@verdurent.com>
Sent: Monday, June 7, 2021 2:01 PM
To: yocto@lists.yoctoproject.org; wojciech.zmuda@huawei.com;
andrei.gherzan@huawei.com; Saini, Naveen Kumar
<naveen.kumar.saini@intel.com>
Cc: Amit Kucheria <amit.kucheria.ext@huawei.com>
Subject: [meta-zephyr][PATCHv2 1/5] zephyr-kernel: Clone mbedtls

From: Amit Kucheria <amit.kucheria.ext@huawei.com>

MBed TLS is a library that implements cryptographic primitives and
SSL/TLS and DTLS protocols that are needed in secure network
communications.

Add it to the kernel include files to build and link against
applications that need mbedtls.

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>
---
recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 1 +
recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc | 1 +
recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc | 1 +
3 files changed, 3 insertions(+)

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
index 330fe59aebe5..c9acbbbc3645 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
@@ -28,6 +28,7 @@ ZEPHYR_MODULES = ""
ZEPHYR_MODULES_append_arm = "\;${S}/modules/cmsis"
ZEPHYR_MODULES_append_nordic = "\;${S}/modules/hal/nordic"
ZEPHYR_MODULES_append_stm32 = "\;${S}/modules/hal/stm32"
+ZEPHYR_MODULES_append_mbedtls = "\;${S}/modules/lib/mbedtls"
ZEPHYR_MODULES_append_openamp = "\;${S}/modules/lib/open-
amp\;${S}/modules/hal/libmetal"

EXTRA_OECMAKE_append = " -
DZEPHYR_MODULES=${ZEPHYR_MODULES}"
diff --git
a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc
b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc
index 5d66f0f3cb5b..3aeb3bf6fc3f 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc
@@ -6,6 +6,7 @@ SRCREV_stm32 =
"cc8731dba4fd9c57d7fe8ea6149828b89c2bd635"
SRCREV_open-amp = "de1b85a13032a2de1d8b6695ae5f800b613e739d"
SRCREV_libmetal = "9d4ee2c3cfd5f49861939447990f3b7d7bf9bf94"
SRCREV_tinycrypt = "3e9a49d2672ec01435ffbf0d788db6d95ef28de0"
+SRCREV_mbedtls = "5765cb7f75a9973ae9232d438e361a9d7bbc49e7"

PV = "2.5.0+git${SRCPV}"

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
b/recipes- kernel/zephyr-kernel/zephyr-kernel-src.inc
index 1d06d916a1e0..069fa561667c 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
@@ -13,6 +13,7 @@ SRC_URI = "\
git://github.com/zephyrproject-
rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis
\
git://github.com/zephyrproject-
rtos/hal_nordic.git;protocol=https;destsuffix=git/modules/hal/nordic
;n
ame=
nordic \
git://github.com/zephyrproject-
rtos/hal_stm32.git;protocol=https;destsuffix=git/modules/hal/stm32;n
am
e=
stm32 \
+
+ git://github.com/zephyrproject-rtos/mbedtls.git;protocol=https;des
+ ts uf fix=git/modules/lib/mbedtls;name=mbedtls \
git://github.com/zephyrproject-rtos/open-
amp.git;protocol=https;destsuffix=git/modules/lib/open-
amp;name=open
-
amp \
git://github.com/zephyrproject-
rtos/libmetal.git;protocol=https;destsuffix=git/modules/hal/libmetal
;n
ame=l
ibmetal \
git://github.com/zephyrproject-
rtos/tinycrypt.git;protocol=https;destsuffix=git/modules/crypto/tiny
cr
ypt;na
me=tinycrypt \
--
2.25.1


[meta-zephyr][PATCH 10/10] zephyr-kernel-src: drop 2.4.0 support

Naveen Saini
 

v2.6.0 is available now.

Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
---
.../zephyr-kernel/zephyr-kernel-src-2.4.0.inc | 11 -----------
1 file changed, 11 deletions(-)
delete mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.4.0.inc

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.4.0.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.4.0.inc
deleted file mode 100644
index a2a3770..0000000
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.4.0.inc
+++ /dev/null
@@ -1,11 +0,0 @@
-SRCREV_FORMAT = "default_cmsis"
-SRCREV_default = "7a3b253ced7333f5c0269387a7f3ed1dee69739d"
-SRCREV_cmsis = "542b2296e6d515b265e25c6b7208e8fea3014f90"
-SRCREV_nordic = "d8a6ea9695ddf792bb18bb6035c13b1daac5d79c"
-SRCREV_stm32 = "f0e11398128ac9abdff713da5d3035e6c96e9b86"
-SRCREV_open-amp = "de1b85a13032a2de1d8b6695ae5f800b613e739d"
-SRCREV_libmetal = "9d4ee2c3cfd5f49861939447990f3b7d7bf9bf94"
-SRCREV_tinycrypt = "3e9a49d2672ec01435ffbf0d788db6d95ef28de0"
-SRCREV_mbedtls = "aef137b1af8aa7a0f43345c82459254b8832262e"
-
-PV = "2.4.0+git${SRCPV}"
--
2.17.1


[meta-zephyr][PATCH 09/10] zephyr-kernel-src-2.4.0.inc: add srcrev for mbedtls module

Naveen Saini
 

Ref: https://github.com/zephyrproject-rtos/zephyr/blob/zephyr-v2.4.0/west.yml#L93

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

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.4.0.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.4.0.inc
index d1ef80e..a2a3770 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.4.0.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.4.0.inc
@@ -6,5 +6,6 @@ SRCREV_stm32 = "f0e11398128ac9abdff713da5d3035e6c96e9b86"
SRCREV_open-amp = "de1b85a13032a2de1d8b6695ae5f800b613e739d"
SRCREV_libmetal = "9d4ee2c3cfd5f49861939447990f3b7d7bf9bf94"
SRCREV_tinycrypt = "3e9a49d2672ec01435ffbf0d788db6d95ef28de0"
+SRCREV_mbedtls = "aef137b1af8aa7a0f43345c82459254b8832262e"

PV = "2.4.0+git${SRCPV}"
--
2.17.1


[meta-zephyr][PATCH 08/10] zephyr-kernel-src-2.6.0.inc: add srcrev for mbedtls module

Naveen Saini
 

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

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc
index 7ef1697..8475b5b 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc
@@ -6,6 +6,7 @@ SRCREV_stm32 = "f8ff8d25aa0a9e65948040c7b47ec67f3fa300df"
SRCREV_open-amp = "6010f0523cbc75f551d9256cf782f173177acdef"
SRCREV_libmetal = "39d049d4ae68e6f6d595fce7de1dcfc1024fb4eb"
SRCREV_tinycrypt = "3e9a49d2672ec01435ffbf0d788db6d95ef28de0"
+SRCREV_mbedtls = "5765cb7f75a9973ae9232d438e361a9d7bbc49e7"

PV = "2.6.0+git${SRCPV}"

--
2.17.1


[meta-zephyr][PATCH 07/10] zephyr-kernel-src set default preferred version to 2.6.0

Naveen Saini
 

From: Wojciech Zmuda <wojciech.zmuda@huawei.com>

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
---
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 01c87c4..5e43583 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
@@ -22,5 +22,5 @@ SRC_URI = "\
S = "${WORKDIR}/git"

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


[meta-zephyr][PATCH 06/10] zephyr-kernel-src: add 2.6.0 release

Naveen Saini
 

From: Wojciech Zmuda <wojciech.zmuda@huawei.com>

Zephyr 2.6.0 release notes:
https://github.com/zephyrproject-rtos/zephyr/releases/tag/zephyr-v2.6.0

Update the following submodules to most recent revisions:
- hal_nordic:
nrfx_dppi: Fix variable used in logging function
- hal_stm32:
dts/st: use a pull-down for SPI SCK pin
- openamp:
lib: update open-amp lib to release v2021.04.0
- libmetal:
lib: update libmetal to release v2021.04.0 + VERSION path fix

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
---
.../zephyr-kernel/zephyr-kernel-src-2.6.0.inc | 13 +++++++++++++
1 file changed, 13 insertions(+)
create mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc
new file mode 100644
index 0000000..7ef1697
--- /dev/null
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc
@@ -0,0 +1,13 @@
+SRCREV_FORMAT = "default_cmsis"
+SRCREV_default = "79a6c07536bc14583198f8e3555df6134d8822cf"
+SRCREV_cmsis = "c3bd2094f92d574377f7af2aec147ae181aa5f8e"
+SRCREV_nordic = "574493fe29c79140df4827ab5d4a23df79d03681"
+SRCREV_stm32 = "f8ff8d25aa0a9e65948040c7b47ec67f3fa300df"
+SRCREV_open-amp = "6010f0523cbc75f551d9256cf782f173177acdef"
+SRCREV_libmetal = "39d049d4ae68e6f6d595fce7de1dcfc1024fb4eb"
+SRCREV_tinycrypt = "3e9a49d2672ec01435ffbf0d788db6d95ef28de0"
+
+PV = "2.6.0+git${SRCPV}"
+
+SRC_URI_append = " file://0001-x86-fix-efi-binary-generation-issue-in-cross-compila.patch \
+ "
--
2.17.1


[meta-zephyr][PATCH 05/10] zephyr-mqtt-publisher: Add recipe for mqtt publisher

Naveen Saini
 

From: Amit Kucheria <amit.kucheria.ext@huawei.com>

This sample application provides an example of using the the MBEDTLS library.

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
---
recipes-kernel/zephyr-kernel/zephyr-mqtt-publisher.bb | 5 +++++
1 file changed, 5 insertions(+)
create mode 100644 recipes-kernel/zephyr-kernel/zephyr-mqtt-publisher.bb

diff --git a/recipes-kernel/zephyr-kernel/zephyr-mqtt-publisher.bb b/recipes-kernel/zephyr-kernel/zephyr-mqtt-publisher.bb
new file mode 100644
index 0000000..b4e3067
--- /dev/null
+++ b/recipes-kernel/zephyr-kernel/zephyr-mqtt-publisher.bb
@@ -0,0 +1,5 @@
+include zephyr-sample.inc
+
+ZEPHYR_SRC_DIR = "${S}/samples/net/mqtt_publisher"
+
+ZEPHYR_MODULES_append = "\;${S}/modules/lib/mbedtls"
--
2.17.1


[meta-zephyr][PATCH 04/10] zephyr-websocket-client: Add recipe for websocket client

Naveen Saini
 

From: Amit Kucheria <amit.kucheria.ext@huawei.com>

This sample application provides an example of using the the MBEDTLS library.

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
---
recipes-kernel/zephyr-kernel/zephyr-websocket-client.bb | 5 +++++
1 file changed, 5 insertions(+)
create mode 100644 recipes-kernel/zephyr-kernel/zephyr-websocket-client.bb

diff --git a/recipes-kernel/zephyr-kernel/zephyr-websocket-client.bb b/recipes-kernel/zephyr-kernel/zephyr-websocket-client.bb
new file mode 100644
index 0000000..428f75e
--- /dev/null
+++ b/recipes-kernel/zephyr-kernel/zephyr-websocket-client.bb
@@ -0,0 +1,5 @@
+include zephyr-sample.inc
+
+ZEPHYR_SRC_DIR = "${S}/samples/net/sockets/websocket_client"
+
+ZEPHYR_MODULES_append = "\;${S}/modules/lib/mbedtls"
--
2.17.1


[meta-zephyr][PATCH 03/10] zephyr-http-client: Add recipe for http client

Naveen Saini
 

From: Amit Kucheria <amit.kucheria.ext@huawei.com>

This sample application provides an example of using the the MBEDTLS library.

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
---
recipes-kernel/zephyr-kernel/zephyr-http-client.bb | 5 +++++
1 file changed, 5 insertions(+)
create mode 100644 recipes-kernel/zephyr-kernel/zephyr-http-client.bb

diff --git a/recipes-kernel/zephyr-kernel/zephyr-http-client.bb b/recipes-kernel/zephyr-kernel/zephyr-http-client.bb
new file mode 100644
index 0000000..cf3c322
--- /dev/null
+++ b/recipes-kernel/zephyr-kernel/zephyr-http-client.bb
@@ -0,0 +1,5 @@
+include zephyr-sample.inc
+
+ZEPHYR_SRC_DIR = "${S}/samples/net/sockets/http_client"
+
+ZEPHYR_MODULES_append = "\;${S}/modules/lib/mbedtls"
--
2.17.1


[meta-zephyr][PATCH 02/10] zephyr-echo-client: Add recipe for echo client

Naveen Saini
 

From: Amit Kucheria <amit.kucheria.ext@huawei.com>

This sample application provides an example of using the the MBEDTLS library.

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
---
recipes-kernel/zephyr-kernel/zephyr-echo-client.bb | 5 +++++
1 file changed, 5 insertions(+)
create mode 100644 recipes-kernel/zephyr-kernel/zephyr-echo-client.bb

diff --git a/recipes-kernel/zephyr-kernel/zephyr-echo-client.bb b/recipes-kernel/zephyr-kernel/zephyr-echo-client.bb
new file mode 100644
index 0000000..c17e1e7
--- /dev/null
+++ b/recipes-kernel/zephyr-kernel/zephyr-echo-client.bb
@@ -0,0 +1,5 @@
+include zephyr-sample.inc
+
+ZEPHYR_SRC_DIR = "${S}/samples/net/sockets/echo_client"
+
+ZEPHYR_MODULES_append = "\;${S}/modules/lib/mbedtls"
--
2.17.1


[meta-zephyr][PATCH 01/10] zephyr-kernel: Clone mbedtls

Naveen Saini
 

From: Amit Kucheria <amit.kucheria.ext@huawei.com>

MBed TLS is a library that implements cryptographic primitives and
SSL/TLS and DTLS protocols that are needed in secure network
communications.

Add it to the kernel include files to build and link against
applications that need mbedtls.

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
---
recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc | 1 +
recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc | 1 +
2 files changed, 2 insertions(+)

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc
index 5d66f0f..545197f 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc
@@ -6,6 +6,7 @@ SRCREV_stm32 = "cc8731dba4fd9c57d7fe8ea6149828b89c2bd635"
SRCREV_open-amp = "de1b85a13032a2de1d8b6695ae5f800b613e739d"
SRCREV_libmetal = "9d4ee2c3cfd5f49861939447990f3b7d7bf9bf94"
SRCREV_tinycrypt = "3e9a49d2672ec01435ffbf0d788db6d95ef28de0"
+SRCREV_mbedtls = "24d84ecff195fb15c889d9046e44e4804d626c67"

PV = "2.5.0+git${SRCPV}"

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
index b3b9565..01c87c4 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
@@ -13,6 +13,7 @@ SRC_URI = "\
git://github.com/zephyrproject-rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis \
git://github.com/zephyrproject-rtos/hal_nordic.git;protocol=https;destsuffix=git/modules/hal/nordic;name=nordic \
git://github.com/zephyrproject-rtos/hal_stm32.git;protocol=https;destsuffix=git/modules/hal/stm32;name=stm32 \
+ git://github.com/zephyrproject-rtos/mbedtls.git;protocol=https;destsuffix=git/modules/lib/mbedtls;name=mbedtls \
git://github.com/zephyrproject-rtos/open-amp.git;protocol=https;destsuffix=git/modules/lib/open-amp;name=open-amp \
git://github.com/zephyrproject-rtos/libmetal.git;protocol=https;destsuffix=git/modules/hal/libmetal;name=libmetal \
git://github.com/zephyrproject-rtos/tinycrypt.git;protocol=https;destsuffix=git/modules/crypto/tinycrypt;name=tinycrypt \
--
2.17.1


Re: Bitbake failure

Randy MacLeod
 

On 2021-05-31 6:12 p.m., Cris Scott wrote:

Not sure who to ask about this.

Using https://push.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-extended/lighttpd/lighttpd_1.4.59.bb to build lighttpd, bitbake fails, and I receive tons of messages that look like:

 

ERROR: lighttpd-1.4.59-r0 do_package_qa: QA Issue: /usr/lib/mod_staticfile.so contained in package lighttpd-module-staticfile requires libc.so.6(GLIBC_2.4), but no providers found in RDEPENDS_lighttpd-module-staticfile? [file-rdeps]

 

 

Can someone point me in the right direction to resolve this?

Hi Cris,

It's been a while is this still a problem for you?
If not, how did you fix it?


Can you reproduce the error with poky? git://git.yoctoproject.org/poky

What release/commit are you using?

Does it happen when you just run: bitbake lighttpd ?

Does it happen if you mv your sstate-cache (tmp*) directories aside
and do a rebuild?

What's in your local.conf?

For completeness, what is your build host distro (I doubt it matters here.).


I built poky from:
7f3c996d30 (HEAD -> master, origin/master, origin/HEAD) lttng-tools: upgrade 2.12.3 -> 2.12.4

on an Ubu-18.04.3 builder, and both:
$ bitbake lighttpd and
$ bitbake core-image-minimal

worked fine with:

grep -v "^$" conf/local.conf  | grep -v "^#"
MACHINE ??= "qemux86-64"
DISTRO ?= "poky"
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
USER_CLASSES ?= "buildstats image-prelink"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS ??= "\
    STOPTASKS,${TMPDIR},1G,100K \
    STOPTASKS,${DL_DIR},1G,100K \
    STOPTASKS,${SSTATE_DIR},1G,100K \
    STOPTASKS,/tmp,100M,100K \
    ABORT,${TMPDIR},100M,1K \
    ABORT,${DL_DIR},100M,1K \
    ABORT,${SSTATE_DIR},100M,1K \
    ABORT,/tmp,10M,1K"
PACKAGECONFIG_append_pn-qemu-system-native = " sdl"
CONF_VERSION = "1"
IMAGE_INSTALL_append = "lighttpd"

../Randy

 

-Bill

 





-- 
# Randy MacLeod
# Wind River Linux


Re: [meta-realtime][PATCH] layer.conf: set LAYERSERIES_COMPAT with honister

Randy MacLeod
 

On 2021-06-04 8:40 a.m., Bruce Ashfield wrote:
On Fri, Jun 4, 2021 at 8:37 AM Bruce Ashfield via
lists.yoctoproject.org
<bruce.ashfield=gmail.com@lists.yoctoproject.org> wrote:

On Fri, Jun 4, 2021 at 8:27 AM Bruce Ashfield <bruce.ashfield@gmail.com> wrote:

On Thu, Jun 3, 2021 at 11:35 PM Kai <kai.kang@windriver.com> wrote:

On 6/4/21 11:22 AM, Bruce Ashfield wrote:
On Thu, Jun 3, 2021 at 11:06 PM <kai.kang@windriver.com> wrote:
From: Kai Kang <kai.kang@windriver.com>

Replace hardknott with honister in layer.conf which aligns with
oe-core.
I had added this back in April, but apparently didn't push the change.

I also noticed that I've been updating the wrong branch with compatibility.

That should all be fixed now.
Hi Bruce,

Thanks. I have seen your commits.

But 3 items in LAYERSERIES_COMPAT_realtime will cause layer index show
warning:

WARNING: YPCompatibleVersion.name: dunfell gatesgarth hardknott:
length 28 exceeds maximum (25), truncating

Could we only keep the latest LAYERSERIES_CORENAMES (honister) in branch
master, please?
Nope. It is compatible with those releases, so they need to stay. I
see no valid reason to be limited to a certain number of characters.


Or it set in oe-core's layer.conf:

LAYERSERIES_CORENAMES = "hardknott honister"

we just align with it to keep the latest 2, please?
That is just as arbitrary, I'll keep it as-is.
I took a quick look, is this warning coming from the layer index ?
That would be important information to convey when sending changes
like this.
Apologies on this, I see in the follow up email you did mention the
layerindex .. I read completely over that, and had to search up the
warning myself. (my fault, not yours).


That being said, it is a longer fix to get that warning changed, and
I'd rather not break the index, so I dropped to only the last two
releases.

But I do recommend that the layer index be changed (if that is the
cause of the warning), since we shouldn't be adapting to the index ..
it should be adapting to layers.
This point still stands though :D
Created:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=14426

Layerindex should allow longer compatible version names


../Randy


Bruce


Bruce


Bruce


Regards,
Kai


Bruce

Signed-off-by: Kai Kang <kai.kang@windriver.com>
---
conf/layer.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index 007f578..8ae67ba 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -15,6 +15,6 @@ BBFILE_PRIORITY_realtime = "5"
# This should only be incremented on significant changes that will
# cause compatibility issues with other layers
LAYERVERSION_realtime = "1"
-LAYERSERIES_COMPAT_realtime = "hardknott"
+LAYERSERIES_COMPAT_realtime = "honister"
LAYERDEPENDS_realtime = "core openembedded-layer"
LAYERRECOMMENDS_realtime = "meta-realtime-dl (= 3.2)"
--
2.17.1
--
Kai Kang
Wind River Linux

--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II


--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II



--
# Randy MacLeod
# Wind River Linux


Re: bitbake controlling memory use

Trevor Gamblin
 


On 2021-06-07 3:27 p.m., Gmane Admin wrote:
[Please note: This e-mail is from an EXTERNAL e-mail address]

Op 05-06-2021 om 15:35 schreef Gmane Admin:
Op 14-04-2021 om 06:59 schreef Richard Purdie:
On Tue, 2021-04-13 at 21:14 -0400, Randy MacLeod wrote:
On 2021-04-11 12:19 p.m., Alexander Kanavin wrote:
make already has -l option for limiting new instances if load
average is
too high, so it's only natural to add a RAM limiter too.

    -l [N], --load-average[=N], --max-load[=N]
                                Don't start multiple jobs unless
load is
below N.

In any case, patches welcome :)

During today's Yocto technical call (1),
we talked about approaches to limiting the system load and avoiding
swap and/or OOM events. Here's what (little!) i recall from the
discussion, 9 busy hours later.

In the short run, instead of independently maintaining changes to
configurations to limit parallelism or xz memory usage, etc, we
could develop an optional common include file where such limits
are shared across the community.

In the longer run, changes to how bitbake schedules work may be needed.

Richard says that there was a make/build server idea and maybe even a
patch from a while ago. It may be in one of his poky-contrib branches.
I took a few minutes to look but nothing popped up. A set of keywords to
search for might help me find it.

http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/wipqueue4&id=d66a327fb6189db5de8bc489859235dcba306237

This patch resolves a starvation of a particular resource (execution
cores), which is good.
However, the problem I am facing is starvation of another resource (memory).

Cheers,

Richard


I like the idea. Unfortunately the patch doesn't apply to Gatesgarth, so
I couldn't test it. Any chance you would be doing a refresh?

Ok so I refreshed this patch my self and it seems to be working nicely
(3000 out of 4000 tasks complete), except for one thing: do_configure
for cmake-native fails and I don't see why. From the log:

loading initial cache file
xxxxxx/out/linux64/build/tmp/work/x86_64-linux/cmake-native/3.18.2-r0/build/Bootstrap.cmk/InitialCacheFlags.cmake
-- The C compiler identification is GNU 10.3.0
-- The CXX compiler identification is GNU 10.3.0
-- Detecting C compiler ABI info
CMake Error: Generator: execution of make failed. Make command was:
xxxxxx/out/linux64/poky/scripts/make-intercept/make cmTC_68352/fast &&
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: xxxxxx/out/linux64/build/tmp/hosttools/gcc
CMake Error: Generator: execution of make failed. Make command was:
xxxxxx/out/linux64/poky/scripts/make-intercept/make cmTC_f23a0/fast &&
-- Check for working C compiler:
xxxxxx/out/linux64/build/tmp/hosttools/gcc - broken
CMake Error at Modules/CMakeTestCCompiler.cmake:66 (message):
  The C compiler

    "xxxxxx/out/linux64/build/tmp/hosttools/gcc"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir:
xxxxxx/tmp/work/x86_64-linux/cmake-native/3.18.2-r0/build/CMakeFiles/CMakeTmp

    Run Build
Command(s):xxxxxx/out/linux64/poky/scripts/make-intercept/make
cmTC_f23a0/fast && Permission denied
    Generator: execution of make failed. Make command was:
xxxxxx/out/linux64/poky/scripts/make-intercept/make cmTC_f23a0/fast &&

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:7 (project)

Crazy. I don't see why making a complete recipe works fine, while making
a test program during configure fails. Ideas?

When I encountered this failure with the patch, it was because the scripts/make-intercept/make script was not marked as executable. However, there was another failure even after that was changed, claiming that an appropriate Makefile parser was not found on the system, which (strangely) seems to be fixed by correcting the script's hashbang to use python3 instead of python. Please see my other response in this thread for further action.

- Trevor






Re: How to use debug symbols from recipe-dbg package?

Randy MacLeod
 

On 2021-06-07 12:01 p.m., Mauro Ziliani wrote:
Hi all.
I have the recipe myapp.bb, and I get from it the debian packages myapp_1.0-r0_armhf.deb and myapp-dbg_1.0-r0_armhf.deb

How can I use the debug symbols in myapp-dbg_1.0-r0_armhf.deb with gdb and the application in myapp_1.0-r0_armhf.deb package?

Hi Mauro,


I'm not sure that I understand. Why wouldn't you just install the dbg deb along with gdb and debug on target?

You might also want to look at using debuginfod if you are on the
hardknott or master branch:

https://pretalx.com/yocto-project-summit-2021/talk/ADCYJ7/

https://www.youtube.com/watch?v=S3QLr113mx8


Did you follow the YP docs:

http://docs.yoctoproject.org/dev-manual/common-tasks.html#debugging-with-the-gnu-project-debugger-gdb-remotely

?

../Randy




Best regards,
  MZ

Sent from Mailspring, the best free email app for work




-- 
# Randy MacLeod
# Wind River Linux


Re: bitbake controlling memory use

Trevor Gamblin
 


On 2021-06-05 9:35 a.m., Gmane Admin wrote:
[Please note: This e-mail is from an EXTERNAL e-mail address]

Op 14-04-2021 om 06:59 schreef Richard Purdie:
On Tue, 2021-04-13 at 21:14 -0400, Randy MacLeod wrote:
On 2021-04-11 12:19 p.m., Alexander Kanavin wrote:
make already has -l option for limiting new instances if load average is
too high, so it's only natural to add a RAM limiter too.

    -l [N], --load-average[=N], --max-load[=N]
                                Don't start multiple jobs unless load is
below N.

In any case, patches welcome :)

During today's Yocto technical call (1),
we talked about approaches to limiting the system load and avoiding
swap and/or OOM events. Here's what (little!) i recall from the
discussion, 9 busy hours later.

In the short run, instead of independently maintaining changes to
configurations to limit parallelism or xz memory usage, etc, we
could develop an optional common include file where such limits
are shared across the community.

In the longer run, changes to how bitbake schedules work may be needed.

Richard says that there was a make/build server idea and maybe even a
patch from a while ago. It may be in one of his poky-contrib branches.
I took a few minutes to look but nothing popped up. A set of keywords to
search for might help me find it.

http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/wipqueue4&id=d66a327fb6189db5de8bc489859235dcba306237

Cheers,

Richard


I like the idea. Unfortunately the patch doesn't apply to Gatesgarth, so
I couldn't test it. Any chance you would be doing a refresh?

I have reworked the patch and I'm doing some testing with it right now. Once I have collected some data (and possibly reworked it further, depending on results), perhaps I can have you test it out as well? That should be in the next day or two.

- Trevor






Re: Managing chinese text input

Randy MacLeod
 

On 2021-06-08 9:17 a.m., Mauro Ziliani wrote:
Hi all.
I'm coding my own keyboard for a touch screen device based on Qt/Qml 5.6.
I'd like to implement a chinese input method.
The keyboard is embedded in the software and it is activated only inside the software.
The system is based on an old mix of Jethro/Krogoth
I know there ibus framework for this, but it is not included in yocto bsp.
Any idea about?
Hi Mauro,

You might have to add the meta-gnome layer or copy the recipe into your
own layer:

https://layers.openembedded.org/layerindex/recipe/112490/

Let us know how that works for you.

../Randy

Best regards,
   MZ
Sent from Mailspring <https://urldefense.com/v3/__https://getmailspring.com/__;!!AjveYdw8EvQ!KQT0NMi6tN3MScjQud46rQHVAeiUdZigxi-wsMs_UQvSO4ze-cH1wNBbJdQv1KsQkriUPw$>, the best free email app for work
Sent from Mailspring

--
# Randy MacLeod
# Wind River Linux


Re: [ANNOUNCEMENT] Yocto Project 3.3.1 (hardknott-25.0.1) is Released

Michael Halstead
 

After discussing it we've gone ahead and deleted the hardknott-25.0.0 tag then added hardknott-3.3, and hardknott-3.3.1 tags. 

From now on any release before 3.3 will have the poky version number tags and from the 3.3 release forward we will use branchname-yocto-version tags.

On Tue, May 25, 2021 at 6:12 AM Peter Kjellerstedt <peter.kjellerstedt@...> wrote:
> -----Original Message-----
> From: Richard Purdie <richard.purdie@...>
> Sent: den 25 maj 2021 14:44
> To: Peter Kjellerstedt <peter.kjellerstedt@...>; Vineela
> <vineela.tummalapalli@...>
> Cc: 'yocto@...' <yocto@...>; Michael
> Halstead <mhalstead@...>
> Subject: Re: [yocto] [ANNOUNCEMENT] Yocto Project 3.3.1 (hardknott-25.0.1)
> is Released
>
> On Tue, 2021-05-25 at 12:13 +0000, Peter Kjellerstedt wrote:
> > It seems the ”hardknott-25.0.1” tag is missing for meta-gplv2.
> > The “yoccto-3.3.1” tag is present.
>
> This was deliberate since we've been trying to step away from the
> "poky" version numbers, I'm not sure they add much to anything.
>
> Is there a particular reason you were looking for those?

Well, those are the ones we have traditionally been using. The benefit I see
with them are that they contain the release name. For me as a user, it is much
easier to see and refer to "hardknott-something.1" than "yocto-3.3.1". I.e.,
I don't have a relation to the "25.0" or "3.3" part, but to the release name.
We typically only talk about "hardknott" or "the second hardknott release".

That said, a tag such as "yocto-hardknott-3.3.1" or "hardknott-3.3.1" would
fulfill the same properties as "hardknott-25.0.1", though the one without
the "yocto-" prefix is more suitable when tab completing, e.g.,
`git log hardknott-3.3..hardknott-3.3.1`, so that is the one I would use if
it was up to me. ;)

> Cheers,
>
> Richard

//Peter



--
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer

1681 - 1700 of 55458