Hi all,
I`m trying to debug coredump generated on embedded system running dunfel.

The issue I`m facing is with the source files path in "-dbg.rootfs" archive and within dedug portion of a package.
When loaded in QtCreator some sources can`t be found :
The part is missing is "*build/..*". Such notation is obviosly cancels itself and adding empty "build" folder manually helps.
This path allings with how it builds. Here is a part of Makefile found in build path for sqlite:
   build/Makefile:20:VPATH = ../sqlite-autoconf-3310100
   build/Makefile:313:abs_srcdir = /home/bohdan/noah/noah/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/sqlite3/3_3.31.1-r0/build/../sqlite-autoconf-3310100
   build/Makefile:315:abs_top_srcdir = /home/bohdan/noah/noah/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/sqlite3/3_3.31.1-r0/build/../sqlite-autoconf-3310100
   build/Makefile:358:srcdir = ../sqlite-autoconf-3310100
So I tried to disable out-of-tree build for sqlite by replacing *'inherit autotools*' with '*inherit autotools-brokensep*'. After building and loading new debugfs QtCreator was able to found required sources:
Is this a known issue or me doing something wrong with build setup?

Since the recent patch to switch to UUIDs [0aa5e600: "use uuid
instead of hard-coding root device"] wic fstab-update is not able
to get the correct value for the used device anymore and falls to
the default 'sda'. Thus wrong /dev/sda entries are generated in fstab.

For partitions that should be updated automatically this can be avoided
by either generate entries using uuid or label.

Signed-off-by: MarkusVolk <f_l_k@...>
---
wic/rockchip.wks | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Add a common override for both nanopi-m4 MACHINEs.

Signed-off-by: Trevor Woerner <twoerner@...>
---
conf/machine/include/nanopi-m4.inc | 3 +++
1 file changed, 3 insertions(+)

There is no "nanopi-m4" defined in any yocto kernel metadata (yet?), therefore
remove this superfluous line.

Build (core-image-base) and run tested (both systemd and sysvinit) on:
- nanopi-m4

Signed-off-by: Trevor Woerner <twoerner@...>
---
conf/machine/include/nanopi-m4.inc | 1 -
1 file changed, 1 deletion(-)

Now that we're booting via UUID, we no longer need these aliases in the DT.
Personally I wasn't able to prove to myself that they actually worked (at
least not with 5.13.y) and fiddling with these aliases didn't seem to affect
the mmc probe order on boot. Additionally it looks like some of these aliases
will be landing upstream shortly.

Build (core-image-base) and run tested (both systemd and sysvinit) on:
- rock64
- rock-pi-e

(i.e. the two rk3328 MACHINEs)

Signed-off-by: Trevor Woerner <twoerner@...>
---
...an-dtsi-rk3328-add-mmc0-mmc1-aliases.patch | 27 -------------------
recipes-kernel/linux/linux-yocto%.bbappend | 3 ---
2 files changed, 30 deletions(-)
delete mode 100644 recipes-kernel/linux/files/0001-ayufan-dtsi-rk3328-add-mmc0-mmc1-aliases.patch

Hi all,
I`m trying to debug coredump generated on embedded system running dunfel. The issue I`m facing is with the source files path in "-dbg.rootfs" archive and within dedug portion of a package.
When loaded in QtCreator some sources can`t be found :
The part is missing is "*build/..*". Such notation is obviosly cancels itself and adding empty "build" folder manually helps.
This path allings with how it builds. Here is a part of Makefile found in build path for sqlite:
   build/Makefile:20:VPATH = ../sqlite-autoconf-3310100
   build/Makefile:313:abs_srcdir = /home/bohdan/noah/noah/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/sqlite3/3_3.31.1-r0/build/../sqlite-autoconf-3310100
   build/Makefile:315:abs_top_srcdir = /home/bohdan/noah/noah/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/sqlite3/3_3.31.1-r0/build/../sqlite-autoconf-3310100
   build/Makefile:358:srcdir = ../sqlite-autoconf-3310100
So I tried to disable out-of-tree build for sqlite by replacing *'inherit autotools*' with '*inherit autotools-brokensep*'. After building and loading new debugfs QtCreator was able to found required sources:
Is this a known issue or me doing something wrong with build setup?

Hi, I'm building a yocto release from the thud branch. The size of the OS image is very critical, so I need to remove as much as I can. Looking at the dependency information, I can see that the "file" package is not required by any other package, but yet it is installed. I really have to remove this package because it is quite large with its magic database, but I can't find who is installing it and why.

I am compiling in 32 bit mode.



From: Khem Raj <raj.khem@...>
Sent: Monday, October 4, 2021 5:15 PM
To: Greg Wilson-Lindberg <GWilson@...>
Cc: yocto@...
Subject: Re: [yocto] virtual/egl on Raspberry Pi 4



It should have automatically found user land package as one of providers but if it is not doing so that means it’s being ignored because it’s not compatible arch or something

Are you compiling 32bit mode ?





On Mon, Oct 4, 2021 at 4:08 PM Greg Wilson-Lindberg <GWilson@...> wrote:

Hi Khem,
Yes, the Raspberry Pi boards do use closed source drivers. What I need is how do I include the proper package that will bring in the necessary virtual/egl for the Raspberry Pi 4.

Greg

-----Original Message-----
From: Khem Raj <raj.khem@...>
Sent: Monday, October 4, 2021 14:17
To: Greg Wilson-Lindberg <GWilson@...>;
yocto@...
Subject: Re: [yocto] virtual/egl on Raspberry Pi 4



On 10/4/21 12:39 PM, Greg Wilson-Lindberg wrote:

Hello list,

I'm working on a Qt supplied boot2qt Yocto build currently based on
Zeus that is running on a Raspberry Pi 4. I recently updated the qt
version to 5.15.6 and Qt changed something in the Yocto configuration
that they are using and now one of the recipes that we use is failing
saying that in needs 'virtual/egl' but that it is not provided by any recipe.

In the searching that I have done I have found that the raspberry pi 4
is particular on which package supplies the virtual/egl but I haven't
seen anything that indicates what I should do to re-enable it.

Can anyone tell me what I need to do to enable the correct driver to
get virtual/egl provided on the Raspberry Pi 4? Or maybe even better,
how I could search through the packages that are enabled on the old
and new Yocto trees so that I can figure out what changed between the
releases and re-enable the virtual/egl.

it should be provided by userland package if you are using closed source
graphics driver.

Best Regards,

Greg Wilson-Lindberg

This is only cover letter, I do not see patches on mailing list..

Regards,
Naveen

-----Original Message-----
From: yocto@... <yocto@...> On
Behalf Of Arnaud Pouliquen
Sent: Wednesday, September 29, 2021 5:41 PM
To: yocto@...
Cc: Kumar Gala <kumar.gala@...>; Kevin Townsend
<kevin.townsend@...>
Subject: [yocto] [meta-zephyr 0/2] add support of the zephyr-openamp-rsc-
table sample on STM32MP157

Add capability to genereate the "zephyr-openamp-rsc-table" sample in yocto
build.

This example demonstrates inter-processor communication based on a
resource table, with the objective of responding to the Linux kernel rpmsg
sample.

This sample is compatible with the stm32mp157c_dk2 board.
The support of the board is also added in this series.

Arnaud Pouliquen (2):
conf: machine: add stm32mp157c-dk2 support
zephyr-kernel: add openamp-rsc-table sample

conf/machine/stm32mp157c-dk2.conf | 8 ++++++++
.../zephyr-kernel/zephyr-openamp-rsc-table.bb | 10 ++++++++++
2 files changed, 18 insertions(+)
create mode 100644 conf/machine/stm32mp157c-dk2.conf create mode
100644 recipes-kernel/zephyr-kernel/zephyr-openamp-rsc-table.bb

--
2.17.1

Greetings !

I could able to add Mosquitto in Yocto Zeus , but as default websockets
is disabled in Mosquitto . Can anyone help me how to enable websockets
in Mosquitto in yocto zeus.

Thanks in Advance

On 9/19/21 12:19 PM, Bhupesh Sharma wrote:

fscrypt is a high-level tool for the management of Linux
filesystem encryption. fscrypt manages metadata, key generation,
key wrapping, PAM integration, and provides a uniform interface
for creating and modifying encrypted directories.

Add recipe for the same in 'recipes-security'.

Was this a double post? or a V2?

I follow the OE/YP Stable process and this appears to be adding a new
package to a stable release which is not allowed.. I have no issue
taking it for Master.

-armin

Signed-off-by: Bhupesh Sharma <bhupesh.sharma@...>
---
recipes-security/fscrypt/fscrypt_1.0.0.bb | 49 +++++++++++++++++++++++
1 file changed, 49 insertions(+)
create mode 100644 recipes-security/fscrypt/fscrypt_1.0.0.bb

diff --git a/recipes-security/fscrypt/fscrypt_1.0.0.bb b/recipes-security/fscrypt/fscrypt_1.0.0.bb
new file mode 100644
index 0000000..a70d310
--- /dev/null
+++ b/recipes-security/fscrypt/fscrypt_1.0.0.bb
@@ -0,0 +1,49 @@
+SUMMARY = "fscrypt is a high-level tool for the management of Linux filesystem encryption"
+DESCIPTION = "fscrypt manages metadata, key generation, key wrapping, PAM integration, \
+and provides a uniform interface for creating and modifying encrypted directories. For \
+a small, low-level tool that directly sets policies, see fscryptctl \
+(https://github.com/google/fscryptcl)."
+HOMEPAGE = "https://github.com/google/fscrypt"
+SECTION = "base"
+LICENSE = "Apache-2.0"
+LIC_FILES_CHKSUM = "file://src/${GO_IMPORT}/LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
+
+BBCLASSEXTEND = "native nativesdk"
+
+# fscrypt depends on go and libpam
+DEPENDS += "go-dep-native libpam"
+
+SRCREV = "92b1e9a8670ccd3916a7d24a06cab1e4c9815bc4"
+SRC_URI = "git://github.com/google/fscrypt.git"
+GO_IMPORT = "import"
+
+S = "${WORKDIR}/git"
+
+inherit go
+inherit goarch
+
+do_compile() {
+ export GOARCH=${TARGET_GOARCH}
+ export GOROOT="${STAGING_LIBDIR_NATIVE}/${TARGET_SYS}/go"
+ export GOPATH="${WORKDIR}/git"
+
+ # Pass the needed cflags/ldflags so that cgo
+ # can find the needed headers files and libraries
+ export CGO_ENABLED="1"
+ export CGO_CFLAGS="${CFLAGS} --sysroot=${STAGING_DIR_TARGET}"
+ export CGO_LDFLAGS="${LDFLAGS} --sysroot=${STAGING_DIR_TARGET}"
+
+ cd ${S}/src/${GO_IMPORT}
+ oe_runmake
+
+ # Golang forces permissions to 0500 on directories and 0400 on files in
+ # the module cache which prevents us from easily cleaning up the build
+ # directory. Let's just fix the permissions here so we don't have to
+ # hack the clean tasks.
+ chmod -R u+w ${S}/pkg/mod
+}
+
+do_install() {
+ install -d ${D}/${bindir}
+ install ${S}/src/${GO_IMPORT}/bin/fscrypt ${D}/${bindir}/fscrypt
+}