This is not something Yocto comes with out of the box, but both rauc and swupdate provides a meta layer you could use. https://github.com/rauc/meta-rauc https://github.com/sbabic/meta-swupdate

Hi, Are there any Yocto recipes to support dual version control for firmware image upgrade and boot? The scenario is to make 2 partitions, one partition to install a work version of image, say v1.0,

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-kernel/linux/linux-yocto-5.0/apparmor.cfg | 6 ------ 1 file changed, 6 deletions(-) diff --git

bug fix release. Signed-off-by: Armin Kuster <akuster808@...> --- .../libseccomp/{libseccomp_2.4.0.bb => libseccomp_2.4.1.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename

Signed-off-by: Armin Kuster <akuster808@...> --- meta-cgl-common/packagegroups/packagegroup-cgl-middleware.bb | 1 - 1 file changed, 1 deletion(-) diff --git

corosync 2.x can replace corosync 1.x + openais. openais is no longer maintainted and shutdown. https://github.com/corosync/openais/commit/f2bc4445a7c4ba5d17a218af855dc19d55ed2803 Signed-off-by:

corosync 1.x have removed from meta-cgl, and use corosync under meta-networking. corosync 2.x can replace corosync 1.x + openais (in meta-cgl), so remove depend on openais Signed-off-by: Armin

Yes, the image will be deployed on the CI to build our software. I managed to just drop the files at some place, but it requires user input to install the compiler. Simon

Why don't you use the layer that comes with the Intel compiler? Ross

Hi, I'm currently working on repackaging the 2016 Intel compiler and I am stuck at the dependency resolution. I am basing my recipe on the AUR PKGBUILD [1], which extracts the RPMs from the

Hi Andrea, Great. I can bring some wooden blocks to prop up the rear-end. People could sit in it and spin the wheels. :rjs -- ----- Rudolf J Streif CEO/CTO ibeeto +1.855.442.3396 x700

Hi Rudi, That's awesome! I will check with LF events to see if there are any issues with showing that or restrictions with how people engage with it during the show. Definitely in favor of showing

Hi Andrea, I was intending to bring the whole gokart. It's more fun to see the speedometer go up when you push down on the pedal and the regen to kick in when letting go etc. Everybody has seen

Hi Rudi, That sounds super interesting. We do have a 6'x6' exhibit booth on the show floor, and a DevDay on Tuesday, August 20. Are you planning to show just the instrument cluster, or the whole

hi Rudolf, +Andreea (Yocto Advocacy) we are definitely planning to be at ELC, with a similar setup as with past ELC : booth, demo, DevDay and BoF, well, at least ! cheers nico

I confirm - this line is not required (at least at Yocto 2.6). Best regards, Lukasz Zemla

I confirm - this line is not required (at least at Yocto 2.6). Best regards, Lukasz Zemla *** The information in this email is confidential and intended solely for the individual or entity to whom

as a followup, i would think that "meta-openembedded" is the canonical example of a container layer, no? rday -- ======================================================================== Robert

much snipping ... uh, i'm looking at meta-virtualization right now: https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/tree/ and that looks like a regular BSP layer, not a container

I apologize if I missed any communication on this mailing list but what are the plans for a presence of YP at ELC NA in August in San Diego this year? Unfortunately, I missed the deadline for