Signed-off-by: Armin Kuster <akuster808@...> --- recipes-core/packagegroup/packagegroup-core-security.bb | 2 -- 1 file changed, 2 deletions(-) diff --git

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-security/scapy/files/run-ptest | 4 --- recipes-security/scapy/python3-scapy_2.4.5.bb | 30 ------------------- 2 files changed,

Signed-off-by: Armin Kuster <akuster808@...> --- .../initrdscripts/initramfs-framework.inc | 16 ++++++++++++++++ .../initramfs-framework_1.0.bbappend | 17 +---------------- 2

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-kernel/linux/linux-%_5.%.bbappend | 4 ---- 1 file changed, 4 deletions(-) delete mode 100644

Signed-off-by: Armin Kuster <akuster808@...> --- recipes-core/busybox/busybox/head.cfg | 1 - recipes-core/busybox/busybox_%.bbappend | 1 - recipes-core/busybox/busybox_libsecomp.inc |

use meta-intel build for a core-i7 I also have an ASUS ROG board running yocto. On 5/30/21 6:15 PM, a.elgammal2019@... wrote:

I am building a custom image for ASUS ROG STRIX Z390-I, with Tesla T4I will build on meta-intel. But the problem is that I am also using Tesla T4 GPU, which requires CUDA toolkit to install. And

Hello, I have a ROG STRIX Z390-I motherboard with an Intel® Z390 chipset. And I want to create a custom BSP Layer for it. Where should I start? I did not find any yocto community for ASUS. So, Any

It looks like a Mesa dependency is looming for NVIDIA: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9902 Thanks

Thanks, it took me a moment to understand that this still does not mean that nvidia supports gbm somehow, somewhere, but rather that virgl needs to be explicit about needing gbm. The patch should be

This addresses cases where the platform doesn't depend on Mesa. Tegra is one example. From 427d6248379bf37f5522d4bb1013b8c0b7a26b5b Mon Sep 17 00:00:00 2001 From: Joel Winarske

Typo. No leading space INIT_MANAGER = "sysvinit". Thanks, Priya.

I got the idea from reading https://docs.yoctoproject.org/ref-manual/migration-3.0.html?highlight=init_manager#init-system-selection But this is exactly why we need some explicit examples.

you don't want the leading space. rday

Is it INIT_MANAGER = " sysvinit" , or INIT_MANAGER = "sysvinit" (no blank at the beginning)? Thank you, Zee _______ <sayinswapna@...> wrote:

Thanks Robert and Raj!! I am using Yocto 3.1 Dunfell release. You are right about the .bbappend file. Changed the name in the overlay to new-ver.bbappend and no longer see the warning. Tried setting

Why do I (always) point out the obvious? And I do need... Geniuses are not meant to fix The World to understand them!? Geniuses should understand The World (and act properly)! Extras to geniality,

Hi Quentin, obviously I didn't read that page carefully enough. Sorry for the noise and thanks for the hint. Cheers, Manuel Am Fr, 28. Mai 2021, um 11:35, schrieb Quentin Schulz:

Hi Manuel, There is an example in the commit you sent, so I would say: SSTATE_MIRRORS ?= " \ file://.* http://someserver.tld/share/sstate/PATH;user=username:password;downloadfilename=PATH

Hello all, to speed up builds, we would like to make the CI generated sstate-cache available via internet. Due to IP concerns, we don't want to make it publically available but for authenticated