I have been inactive for an extended period. Signed-off-by: Philip Tricca <flihp@...> --- MAINTAINERS | 5 ----- 1 file changed, 5 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index

Hi can you please help out with following issue ERROR: core-image-minimal-1.0-r0 do_rootfs: Postinstall scriptlets of ['hostapd'] have failed. If the intention is to defer them to first boot,then

I am using zeus, standard SDK, cmake… Can I pre-configure the SDK to setup cmake package search paths ?, say for find_package, etc. (i.e. detecting external libraries/programs)… The

Hello all! Since a certain eeprom version, the Raspberry Pi 4 can directly boot from network. Has anyone experience on this? I already managed to to have the Raspi to load the kernel and all the

Fixes build with gcc 11+ Signed-off-by: Khem Raj <raj.khem@...> --- .../0001-winpthreads-Add-__udivmoddi4.patch | 52 +++++++++++++++++++ .../nativesdk-mingw-w64-winpthreads_8.0.0.bb | 2

Signed-off-by: Khem Raj <raj.khem@...> --- recipes-devtools/mingw-w64/mingw-w64.inc | 2 +- ...64-headers_7.0.0.bb => nativesdk-mingw-w64-headers_8.0.0.bb} | 0

To my way of thinking, a $ devtool modify linux should NEVER fail if it is preceded by $ bitbake -c do_cleanall linux The intended staging of the kernel into the workspace fails, saying that it

Hi, It's very big and probably include your proprietary SW header and libraries at the very least... or third party prebuilt binaries/libraries you're not supposed to share outside of your

Add possibility, via PACKAGECONFIG variable, to enable cryptodev (hardware crypto acceleration) for gnutls in a very similar way as it is already present for openssl. Signed-off-by: Federico

The plan is that today-ish we roll the 3.3 release for hardknott and also tag point releases on the stable branches too. Ross

colleague wants to get into working with SDKs, and as i'm just diving into the intricacies of that myself, i'm not sure how to answser the question: "is there any reason to use the regular SDK

I think its perhaps also that distros have mechanisms to lock layers at a given revision whatever tooling they use ( git submod, android repo, combotools something else) so distro manifest at that

To be honest I don't see much value of these tags for layers not included in the QA testing with oe-core release. I believe we agreed on promoting latest revisions in the branches for selected

The implication here is that the Yocto Project has run QA if this is in response to Khem's statement above, Or am I miss interpreting your recommendation? Now regarding meta-security, I would not

Hi Armin, The community will fix bugs on HEAD just like before. It's a tag indicating where the branch was at GA time. There's no obligation for he maintainer do do anything in addition to what they

So do you plan on doing the dot releases too? -armin

When we actually release, yes. Ross

That could open up a can of worms as who will fix the QA test failures? -armin

How about: https://git.openembedded.org/meta-openembedded/commit/?id=71b546ed8595b14d29efc1e8b951f8c845ad10c4 ../Randy -- # Randy MacLeod # Wind River Linux

It doesn't have a yocto-3.3 tag yet... Could you add one? ../Randy -- # Randy MacLeod # Wind River Linux