Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.9.rc1)

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.9.rc1 We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. Coffee Lake 3. NUC 7

[yocto] Yocto Technical Team Minutes, Engineering Sync, for June 22, 2021

Yocto Technical Team Minutes, Engineering Sync, for June 22, 2021 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == disclaimer == Best efforts are made to ensure the below is accurate and valid. However, errors sometimes happen. If any errors or

[yocto-announce] [ANNOUNCEMENT]Milestone 1 for Yocto Project 3.4 (yocto-3.4_M1) now available

Hello, We are pleased to announce the first milestone release for Yocto Project 3.4 (yocto-3.4_M1) is now available for download. Download: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.4_M1 bitbake: 398a1686176c695d103591089a36e25173f9fd6e meta-arm:

[yocto] [ANNOUNCEMENT]Milestone 1 for Yocto Project 3.4 (yocto-3.4_M1) now available

Hello, We are pleased to announce the first milestone release for Yocto Project 3.4 (yocto-3.4_M1) is now available for download. Download: http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.4_M1 bitbake: 398a1686176c695d103591089a36e25173f9fd6e meta-arm:

[yocto] QA notification for completed autobuilder build (yocto-3.1.9.rc1)

A build flagged for QA (yocto-3.1.9.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.1.9.rc1 Build hash information: bitbake: 0e0af15b84e07e6763300dcd092b980086b9b9c4 meta-arm: 59974ccd5f1368b2a1c621ba3efd6d2c44c126dd

[yocto] Yocto Project Status WW25`21

Current Dev Position: YP 3.4 M2 Next Deadline: 12th July 2021 YP 3.4 M2 build Next Team Meetings: * Bug Triage meeting Thursday June 24th at 7:30am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)

[linux-yocto] [PATCH 2/3] nxp-imx8: Enable the depended kernel options

Some kernel options have dependency on other options, we should also enable them otherwise we would observe the following warnings: 'CONFIG_ARM_CPUIDLE' last val (y) and .config val (n) do not match 'CONFIG_LEDS_TRIGGER_DISK' last val (y) and .config val (n) do not match 'CONFIG_VIDEO_MXC_CAPTURE'

[linux-yocto] [PATCH 3/3] nxp-imx8: Delete the obsolete kernel options

Delete some kernel configurations of DPAA2, ACPI and GPIO, these configurations are not used, so there is no need to open them Signed-off-by: Xiaolei Wang --- bsp/nxp-imx8/nxp-imx8.cfg | 26 -- 1 file changed, 26 deletions(-) diff --git a/bsp/nxp-imx8/nxp-imx8.cfg

[linux-yocto] [PATCH 1/3] nxp-imx8: Drop the redundant kernel options

CRYPTO_CBC has been selected as Y by XFRM_ESP, CRYPTO_CTS and CRYPTO_XTS have been selected as Y by FS_ENCRYPTION_ALGS, CONFIG_CRYPTO_MD4, CONFIG_CRYPTO_MD5 and CONFIG_CRYPTO_SHA512 have been selected as Y by CIFS. Therefore, these configurations do not need to be enabled in the kernel config

[linux-yocto][yocto-kernel-cache][master yocto-5.13][PATCH] kfence: Initial enablement

Kernel Electric-Fence (KFENCE) is a low-overhead sampling-based memory safety error detector. KFENCE detects heap out-of-bounds access, use-after-free, and invalid-free errors. KFENCE is designed to be enabled in production kernels, and has near zero performance overhead. Compared to KASAN,

[yocto] Update APTCONF_TARGET manually

Hi all I move all TMPDIR in another folder The EXTRA_DISTRO_FETAURES += "package_managent" PACKAGE_CLASS := " package_deb " When I build the image the package_manager try to find the debs in the older folder. I see that this problem is in apt/apt.conf of image working dir. How can I change

Re: [yocto] Empty source package when using devtool

Hello, I dug further into yocto classes and I think I found what is going on. All seems to come from the fact that gcc debug-prefix-map and macro-prefix-map options are statically defined in bitbake.conf to > > DEBUG_PREFIX_MAP ?= >