I was not sure of if it will break some use cases therefore I just wanted to add what works and not delete anything I have not tested

Applied to meta-rockchip master branch, thanks!

Hi Khem, Considering that we have a branch for kirkstone already, maybe we can just switch to supporting langdale only? Cheers, Quentin

* the next release 4.2 will be named mickledore Signed-off-by: Martin Jansa <Martin.Jansa@...> --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

“This folder is empty” Ross

Hi Michael, google link doesn't work. Without seeing source hard to say what it can be but it looks like typo or so as float numbers use only one '.' ;) Which poky version do you use? Do you use a

Signed-off-by: Yi Zhao <yi.zhao@...> --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index d6f83c9..5673b73

Signed-off-by: Jon Mason <jon.mason@...> --- meta-zephyr-bsp/conf/layer.conf | 4 ++-- meta-zephyr-core/conf/layer.conf | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git

Signed-off-by: Khem Raj <raj.khem@...> --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index a2661f9..0e28857

Hello, I work on OpenBMC and am having an issue with EXTRA_IMAGECMD:squashfs-xz. There was a recent change pulled into OpenBMC in image_types.bbclass. In the old file, IMAGE_CMD:squashfs-xz was

Hello, I have an application that is comprised of C++ and C code modules. I have two bitbake builds, prod and dev. The dev image builds 100% of the time. The difference between prod and dev, dev has

Hello, I have an application that is comprised of C++ and C code modules. I have two bitbake builds, prod and dev. The dev image builds 100% of the time. The difference between prod and dev, dev has

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Steve Sakoman, Joshua Watt, Richard Purdie, Alexandre Belloni, Stephen Jolley, Ross Burton, Tim Orling, Alexandre

I probably should've added this to the patch before submitting, but the CI pipeline is https://gitlab.com/jonmason00/meta-zephyr/-/pipelines/654297811

zephyr-openthread-rcp support was recently added to nrf52840-mdk-usb-dongle and nrf52840dk-nrf52840. Add this to the targets for both machines, which necessitates adding a target entry for

We probably need to add "zephyr-openthread-rcp" to the yml file as well (to verify it compiles as part of CI). Since it is missing for nrf52840dk-nrf52840 too, I'll do a quick patch to add this for

Verified in a batch CI job. See https://gitlab.com/jonmason00/meta-zephyr/-/pipelines/654231304 Tested-by: Jon Mason <jon.mason@...>

I wasn't seeing this issue. So, my "testing" isn't very valid for it, but it did work for me :) Verified in a batch CI job. See

FYI, issue has been resolved upstream