Re: [yocto] Package feeds between different Yocto releases?

No, it's neither tested nor expected to work between major yocto releases. In embedded world the typical way to update a system is to overwrite the whole partition. Some setups use filesystem snapshot approach like ostree. Alex On Tue, 23 May 2023 at 11:22, Ivan Drobyshevskyi wrote: > > Hi, > >

[yocto] [meta-raspberrypi] [meta-qt6] Building qt6 on rpi4

Hello all, I'm using: Kirkstone meta-raspberry meta-qt6 (v6.5) >From this post from Qt they suggest the correct graphics setup for a RPi4 should be: *With the Raspberry Pi 4 example, we expect that EGL, OpenGL ES and EGLFS GBM are all reported

Re: [yocto] [meta-xilinx][PATCH] Use new variable LICENSE_FLAGS_ACCEPTED

On 2023-04-22 22:49, Yu, Mingli wrote: Ping. Thanks, Mingli, Please re-send to: meta-xil...@lists.yoctoproject.org unless someone picks up the change and merges it before your morning. See: https://lists.yoctoproject.org/g/meta-xilinx ../Randy On 4/24/22 11:20, Yu, Mingli wrote: From:

Re: [yocto] Inquiry Regarding License Compatibility in OpenEmbedded Meta-Security Layer #selinux #yocto #qt5 #kernel #hardknott #bitbake #dunfell #gplv3 #imx8 #linux

Alex replied to most of the points already but I want to make this very clear. On 23 May 2023, at 12:30, cheerala.rohith via lists.yoctoproject.org wrote: > 2. Which license will apply to the Image that is bitbaked with openembedded > recipes? will the license be MIT as Yocto project.

[yocto] Yocto Project Status 23 May 2023 (WW21)

Current Dev Position: YP 4.3 M1 Next Deadline: 5th June 2023 YP 4.3 M1 build date Next Team Meetings: * Bug Triage meeting Thursday May 25th 7:30 am PDT (

Re: [yocto] Inquiry Regarding License Compatibility in OpenEmbedded Meta-Security Layer #selinux #yocto #qt5 #kernel #hardknott #bitbake #dunfell #gplv3 #imx8 #linux

On Tue, 23 May 2023 at 13:30, wrote: > > I am reaching out to seek clarification regarding the license compatibility > within theOpenEmbedded Meta-Security layer, particularly in relation to the > presence of LGPL, GPL 2.0 and GPL 3.0 licenses and the ambiguity in the > license information of

[yocto] Inquiry Regarding License Compatibility in OpenEmbedded Meta-Security Layer #selinux #yocto #qt5 #kernel #hardknott #bitbake #dunfell #gplv3 #imx8 #linux

I am reaching out to seek clarification regarding the license compatibility within theOpenEmbedded *Meta-Security layer* , particularly in relation to the presence of *LGPL, GPL 2.0 and GPL 3.0* licenses and the ambiguity in the license information of the ClamAV tool and other Security tools in

[yocto] [meta-tpm][PATCH 1/2] linux-yocto: support tpm and tpm2 on all architectures

From: Mikko Rapeli arm, arm64 and other machines can also have tpm and tpm2 devices and the config snippets tpm.scc and tpm2.scc work there too. Signed-off-by: Mikko Rapeli --- meta-tpm/recipes-kernel/linux/linux-yocto_tpm.inc | 11 +-- 1 file changed, 1 insertion(+), 10 deletions(-)

[yocto] [meta-tpm][PATCH 2/2] linux-yocto: remove tpm_x86.cfg

From: Mikko Rapeli It's not used by linux-yocto bbappends in any configuration. Signed-off-by: Mikko Rapeli --- meta-tpm/recipes-kernel/linux/linux-yocto/tpm_x86.cfg | 4 1 file changed, 4 deletions(-) delete mode 100644 meta-tpm/recipes-kernel/linux/linux-yocto/tpm_x86.cfg diff --git

[yocto] Package feeds between different Yocto releases?

Hi, Are package feed updates (e.g. deb or rpm) between different yocto releases (e.g. dunfell and kirkstone) expected to work/supported? I've tried it briefly and package state differences between the two seem to be a mess. But still, apt somehow managed to update most of the packages, but not

Re: [yocto] core-image-weston mickledore

On Mon, May 22, 2023 at 6:22 PM Khem Raj wrote: > > On Mon, May 22, 2023 at 5:26 AM Marek Belisko wrote: > > > > Hi, > > > > I'm using core-image-weston and adding chromium to the final image. > > Weston is properly started on the hdmi monitor. I'm trying to start > > chromium when weston starts

Re: [yocto] [meta-raspberrypi] [meta-qt6] Building qt6 on rpi4

Looks like I've got a solution. My qtbase_git.bbappend now contains: DISTRO_FEATURES:remove:rpi = " x11 wayland" PACKAGECONFIG:append:rpi = " accessibility eglfs fontconfig gles2 linuxfb tslib gbm" & this now results in an output of bitbake -v -c configure qtbase EGL

[yocto] [yocto-autobuilder2] schedulers: update to add mickledore

Signed-off-by: Steve Sakoman --- schedulers.py | 25 - 1 file changed, 20 insertions(+), 5 deletions(-) diff --git a/schedulers.py b/schedulers.py index 24cbd70..2f7a8ab 100644 --- a/schedulers.py +++ b/schedulers.py @@ -60,6 +60,21 @@ branchdefaults = {

[yocto] Importing environmental variables to receipe #kirkstone

we are working behind the proxy , there are errors while compiling sphinx module in setuptools3 adding python modules. we would like to export the http_proxy and https_proxy in the bb file. I still have the fetch issue .  Are there any suggestion for the same -=-=-=-=-=-=-=-=-=-=-=- Links: You

[yocto] [meta-mingw] [PATCH] mingw32: Add WINDRES export for SDK

GCC-13 has added code where windres is called on a rc file which includes winuser.h, this requires to call windres with -I option to point to right header directory duting gcc-candian-cross builds Fixes

Re: [yocto] Inquiry Regarding License Compatibility in OpenEmbedded Meta-Security Layer #selinux #yocto #qt5 #kernel #hardknott #bitbake #dunfell #gplv3 #imx8 #linux

On 5/23/23 7:53 AM, Alexander Kanavin wrote: On Tue, 23 May 2023 at 13:30, wrote: I am reaching out to seek clarification regarding the license compatibility within theOpenEmbedded Meta-Security layer, particularly in relation to the presence of LGPL, GPL 2.0 and GPL 3.0 licenses and the

[yocto] [ANNOUNCEMENT] Yocto Project 4.0.10 is Released

Hi We are pleased to announce the Yocto Project 4.0.10 Release is now available for download. http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.10/poky-f53ab3a2ff206a130cdc843839dd0ea5ec4ad02f.tar.bz2

[linux-yocto] [std/rt kernel v6.1]: thermal: s32cc: use new API hwmon_device_register_for_thermal() to fix probe error

Hi Bruce, The following patch is to fix s32cc thermal driver probing error issue. Would you please help to merge it into the following: v6.1/standard/nxp-sdk-5.15/nxp-s32g v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g branches? Thanks, Zhantao -=-=-=-=-=-=-=-=-=-=-=- Links:

[linux-yocto] [PATCH] thermal: s32cc: use new API hwmon_device_register_for_thermal() to fix probe error

In s32cc thermal driver, the current used hwmon_device_register_with_info() API, is not suitable for s32cc anymore, due to the commit ddaefa209c4a ("hwmon: Make chip parameter for with_info API mandatory"), or else, there will be probe error when load the driver. And for thermal subsystem, commit

Re: [linux-yocto][v5.10/standard/preempt-rt/*] fix preempt-rt compile error

In message: [linux-yocto][v5.10/standard/preempt-rt/*] fix preempt-rt compile error on 22/05/2023 Li Wang wrote: > Hi Bruce, > > I think the 2 patches should also merge to: > https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git/log/?h=v5.10-rt-next > >

Re: [linux-yocto][yocto-kernel-cache][yocto-6.1] cgl: checkreqprot is deprecated, drop CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE

In message: [linux-yocto][yocto-kernel-cache][yocto-6.1] cgl: checkreqprot is deprecated, drop CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE on 22/05/2023 Xiangyu Chen wrote: > From: Xiangyu Chen > > checkreqprot has been dropped, if turn on this config, kernel would report an > error

Re: [linux-yocto][v5.10/standard/nxp-sdk-5.10/nxp-soc & v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-soc][PATCH] qoriq_thermal.c: crash of error device pointer value

merged. Bruce In message: [linux-yocto][v5.10/standard/nxp-sdk-5.10/nxp-soc & v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-soc][PATCH] qoriq_thermal.c: crash of error device pointer value on 22/05/2023 Li Wang wrote: > qoriq_tmu_probe -> > qoriq_tmu_register_tmu_zone -> >

Re: [linux-yocto] [std/rt kernel v6.1]: thermal: s32cc: use new API hwmon_device_register_for_thermal() to fix probe error

In message: [linux-yocto] [std/rt kernel v6.1]: thermal: s32cc: use new API hwmon_device_register_for_thermal() to fix probe error on 23/05/2023 Zhantao Tang wrote: > Hi Bruce, > > The following patch is to fix s32cc thermal driver probing error issue. > Would you please help to merge it into

[yocto-announce] [ANNOUNCEMENT] Yocto Project 4.0.10 is Released

Hi We are pleased to announce the Yocto Project 4.0.10 Release is now available for download. http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.10/poky-f53ab3a2ff206a130cdc843839dd0ea5ec4ad02f.tar.bz2