Hello IIRC you can prepare configuration for Zeus and run build, lots of things probable will need to be rebuild as there will be in different versions but if only U-Boot is a problem then maybe you

Hello everyone, Say I built Yocto for the latest build for instance Hardknott. Let’s say I need to build for Zeus instead (and hopefully keep everything I built [that doesn’t need to be

Richard,

3.4.2 rc1 was built on the autobuilder. It didn't send the QA email as that is broken. I haven't sent it manually as we need to decide what to do with this build. There was one failure and 8

Hi Rayaan, Currently DKMS is not supported in Yocto/OE and there are no imminent plans to change that. See the discussion on the topic at

Good day, I am new to yocto and in need of assistance please. Could someone please assist me with getting DKMS included in my build. my platform is: stm32mp1

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.14.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1.

I agree, this either needs input from the community in order to drive it or a sponsor. It will be interesting to see if people are interested in doing this and I guess we can gauge that from the

I suspect the eSDK adds a workspace for the devtool and similar workflows so that piece may be normal and perhaps it was conflicting with your existing workspace? I have to admit I don't remember if

Richard,

I'm now wondering what happens if you remove   <my_home_dir>/poky/poky-build/workspace \ since I suspect your local workspace probably doesn't make sense in the eSDK? Could you try temporarily

Hello Khem, Doing "bitbake -e core-image-swupdate | grep ^INIT_MANAGER=" shows INIT_MANAGER="none". And "bitbake -e core-image-swupdate | grep ^DISTRO_FEATURES=" shows DISTRO_FEATURES="acl alsa argp

Richard,

Sorry, I'm getting confused here with earlier work Michael Ho did at BMW. The links here: https://lists.yoctoproject.org/g/yocto/message/52650 https://github.com/bmwcarit/meta-abicompat are the

That's true, this will require engagement from the community. Tool could take few iterations to perfect. Until then, I expect tool owner to be responsible for fixing these bugs. Once stability is

Thanks, I'm not seeing anything too odd there. I guess next we need to see the bblayers.conf that the code is building into the eSDK and compare it to your original conf/bblayer.conf. The generated

You're after our LTS to maintain ABI. In order to do that we need help, not just with patches generating some output, but in day to day running of the project, i.e. help comparing output before and

What would be the minimum acceptable solution with the least investment? in other words, do we have a list of requirements? Our team has posted a solution. BMW folks posted a solution. None of them

Richard,

I think its not that LTS itself but also upgrade from LTS to LTS or other newer versions, it wouuld be good to have this tool and prerhaps a list of API/ABI changes to help migration/upgrade to newer