[yocto] Common directory creation between recipes #dunfell

Hi, I'm wondering if there is a mechanism I could utilize to create target directories in one place that is shared between recipes? I have an image that has multiple packages being created and installed in the same directory. It has worked so far, but its fragile. Adding a new recipe that

[yocto] M+ & H bugs with Milestone Movements WW17

All, YP M+ or high bugs which moved to a new milestone in WW17 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 12272 Create new test cases for Kernel Development features

[yocto] Enhancements/Bugs closed WW17

All, The below were the owners of enhancements or bugs closed during the last week! Who Count randy.macl...@windriver.com 5 tim.orl...@konsulko.com 2 ross.bur...@arm.com 1 richard.pur...@linuxfoundation.org 1 mhalst...@linuxfoundation.org 1 Grand Total 10 Thanks, Stephen

Re: [linux-yocto][v5.10/standard/preempt-rt/base][PATCH] tcp: Fix net/ipv4/inet_hashtables.c conflict

On Mon, Apr 25, 2022 at 5:21 AM He Zhe wrote: > > This causes build failure. > Keep all parts of the function from v5.10/standard/base I still had this round of updates under test, and yes, this is consistent with my local fixup, which matches what 5.18-rt did to the same function. Bruce > >

[yocto] Current high bug count owners for Yocto Project 4.1

All, Below is the list as of top 40 bug owners as of the end of WW17 of who have open medium or higher bugs and enhancements against YP 4.1. There are 130 possible work days left until the final release candidates for YP 4.1 needs to be released. Who Count michael.opdenac...@bootlin.com

Re: [linux-yocto] Build failure drivers/video/fbdev/core/fbmem.c

On Mon, Apr 25, 2022 at 8:33 AM Bruce Ashfield via lists.yoctoproject.org wrote: > > On Mon, Apr 25, 2022 at 1:23 AM He Zhe wrote: > > > > Hi Bruce, > > > > The base context of 2388f826cdc9af2651991adc0feb79de9bdf2232 is removed and > > it causes build failure for all branches. > >

Re: [yocto] have busybox prompt for password in initramfs boot

> On 4/23/22 22:56, Embedded 1 wrote: > > when I boot my initramfs and run init=/bin/sh I'm not prompted for a > > password. How can I require a password before entering the shell? > > > That's what you get when you use /bin/sh as the init process. Instead, > you could use the normal init program

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

Re: [yocto] [meta-cgl][PATCH] cgl-init-build-env: Use new variable LICENSE_FLAGS_ACCEPTED

Merged, thanks. On 4/23/2022 8:09 PM, Yu, Mingli wrote: From: Mingli Yu Signed-off-by: Mingli Yu --- cgl-init-build-env | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cgl-init-build-env b/cgl-init-build-env index acf459d..1d51219 100755 --- a/cgl-init-build-env

Re: [yocto] [meta-cgl][PATCH 1/1] LICENSE: update to standard SPDX names

Merged, thanks. On 4/13/2022 1:59 PM, Joe Slater wrote: Use convert-spdx-licenses.py to change LICENSE in two recipes. Signed-off-by: Joe Slater --- meta-cgl-common/recipes-cgl/cluster/cluster_3.2.0.bb | 2 +- meta-cgl-common/recipes-cgl/heartbeat/heartbeat_3.0.6.bb | 2 +- 2 files

[linux-yocto] [PATCH] nxp-ls1046: add scc and cfg files for nxp-ls1046 platform

Add new scc and cfg files for BSP nxp-ls1046 on branch yocto-5.15. Signed-off-by: Meng Li --- bsp/nxp-ls1046/nxp-ls1046-preempt-rt.scc | 8 ++ bsp/nxp-ls1046/nxp-ls1046-standard.scc | 8 ++ bsp/nxp-ls1046/nxp-ls1046.cfg| 156 +++

[linux-yocto] [yocto-kernel-cache]: nxp-ls1046: add scc and cfg files for nxp-ls1046 platform

From: Limeng Hi Bruce, Recently, I am working on nxp ls1046 SoC BSP, and want to add scc and cfg files for this BSP in kernel-cache. Could you please help to merge this patch into yocto-kernel-cache, branch is only yocto-5.15? diffstat info as below: nxp-ls1046-preempt-rt.scc |8 ++

Re: [yocto] [PATCH yocto-autobuilder-helper v8] Add a banner on the old documentation docs.

> > Hardcoding numbers like this isn’t a great idea. If the intention is to > add the warning on all versions earlier than 3.2, then the regex approach > that is commented out would be better. It most likely didn’t work as regex > matching isn’t like shell/windows matching: pattern = r”^3\.1.*" A

Re: [linux-yocto] Build failure drivers/video/fbdev/core/fbmem.c

On Mon, Apr 25, 2022 at 1:23 AM He Zhe wrote: > > Hi Bruce, > > The base context of 2388f826cdc9af2651991adc0feb79de9bdf2232 is removed and > it causes build failure for all branches. >

[yocto] [PATCH yocto-autobuilder-helper] config.json: test only command line images with x32

There has been a persistent stream of graphical failures on x32, and there is doubt about whether x32 is at all used by anyone nowadays - let's reduce the scope of x32 QA, and perhaps later drop it altogether. Signed-off-by: Alexander Kanavin --- config.json | 4 ++-- 1 file changed, 2

[yocto] [meta-zephyr][PATCH] zephyr-openthread-rcp: Enable Thread 1.2 capabilities in RCP build

From: Stefan Schmidt When running an up-to-date userspace component, like otbr-agent or ot-daemon, with Thread 1.2 enabled we need a firmware matching this capabilities. Signed-off-by: Stefan Schmidt --- .../recipes-kernel/zephyr-kernel/zephyr-openthread-rcp.bb | 2 +- 1 file changed, 1

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

Hello everyone, This is the full report for yocto-3.3.6.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults === Summary No high milestone defects. No new issue found. Thanks, Jay > -Original Message- > From:

Re: [yocto] have busybox prompt for password in initramfs boot

Hello On 4/23/22 22:56, Embedded 1 wrote: > when I boot my initramfs and run init=/bin/sh I'm not prompted for a > password. How can I require a password before entering the shell? That's what you get when you use /bin/sh as the init process. Instead, you could use the normal init program built

[linux-yocto][v5.10/standard/preempt-rt/base][PATCH] tcp: Fix net/ipv4/inet_hashtables.c conflict

This causes build failure. Keep all parts of the function from v5.10/standard/base Fixes: f640c7dd08c9 ("Merge branch 'v5.10/standard/base' into v5.10/standard/preempt-rt/base") Signed-off-by: He Zhe --- net/ipv4/inet_hashtables.c | 22 -- 1 file changed, 22 deletions(-)

Re: [yocto] [PATCH yocto-autobuilder-helper v8] Add a banner on the old documentation docs.

Hi Ross, On 4/25/22 10:43, Ross Burton wrote: +from logging import root +import os +import re The logging and re imports are unused, remove these. + + +html_content = ''' +This document is outdated, you should select the

Re: [yocto] [PATCH yocto-autobuilder-helper v8] Add a banner on the old documentation docs.

> +from logging import root > +import os > +import re The logging and re imports are unused, remove these. > + > + > +html_content = ''' > +This document is outdated, you should select the > https://docs.yoctoproject.org/;>latest release version in this > series. > + > +''' > +last_div = ''' >

Re: [yocto] [psplash][RFC PATCH 00/14] Implement DRM backend

Hello Vasyl, can you explain how this was tested? Is it possible to automate with qemu targets? Alex On Mon, 25 Apr 2022 at 10:00, Vasyl Vavrychuk wrote: > > It is needed in case display does not support FB. > > The missing part is drawing splash screen over all connected displays. I think >

[linux-yocto] [PATCH 2/2] driver: net: dpaa: support interface mode usxgmii

According to upsteam commit ce64c1f77a9d("net: phy: aquantia: add USXGMII support and warn if XGMII mode is set "). When using aquantia phy(e.g AQR107), it needs to support usxgmii interface mode in network driver. Signed-off-by: Meng Li --- drivers/net/ethernet/freescale/dpaa/dpaa_eth.c| 3

[linux-yocto]: [kernel/kernel-rt]: nxp-ls1046: support interface mode usxgmii

From: Limeng Hi Bruce, The 2 patches are used to support interface mode usxgmii So, could you please help merge these patches into linux-ycoto kernel, both below 2 branchs? v5.15/standard/nxp-sdk-5.15/nxp-soc v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc diffstat info as below:

[linux-yocto] [PATCH 1/2] arch: arm64: dts: set correct phy-connection-type for aqr107 10G phy

When kernel boots up, there is below warning calltrace: Call trace: aqr107_config_init+0xc8/0xd0 phy_init_hw+0x74/0xd0 phy_attach_direct+0x15c/0x304 phy_connect_direct+0x34/0x90 of_phy_connect+0x6c/0xbc memac_init_phy+0xac/0x178 dpa_start+0x3c/0x134 dpa_eth_priv_start+0xac/0xe0

[yocto] [psplash][RFC PATCH 14/14] psplash-drm.c: Implement double buffering

Based on https://github.com/dvdhrm/docs/blob/master/drm-howto/modeset-double-buffered.c Signed-off-by: Vasyl Vavrychuk --- psplash-drm.c | 176 +++--- 1 file changed, 140 insertions(+), 36 deletions(-) diff --git a/psplash-drm.c b/psplash-drm.c index

[yocto] [psplash][RFC PATCH 09/14] Rework flip as function pointer

It allows making parse_command and psplash_main independent of FB. Signed-off-by: Vasyl Vavrychuk --- psplash-draw.h | 3 +++ psplash-fb.c | 8 +--- psplash-fb.h | 3 --- psplash.c | 16 4 files changed, 16 insertions(+), 14 deletions(-) diff --git

[yocto] [psplash][RFC PATCH 00/14] Implement DRM backend

It is needed in case display does not support FB. The missing part is drawing splash screen over all connected displays. I think there should be loop somewhere for this, but I am not sure which level is the best to put it.

[yocto] [psplash][RFC PATCH 10/14] Import drm-howto modeset.c as psplash-drm.c

Imported as is from repo: https://github.com/dvdhrm/docs.git branch: master commit: fc5c63f path: drm-howto/modeset.c Signed-off-by: Vasyl Vavrychuk --- psplash-drm.c | 735 ++ 1 file changed, 735 insertions(+) create mode 100644 psplash-drm.c

[yocto] [psplash][RFC PATCH 03/14] Remove unused save_termios

Signed-off-by: Vasyl Vavrychuk --- psplash-fb.h | 1 - psplash.h| 1 - 2 files changed, 2 deletions(-) diff --git a/psplash-fb.h b/psplash-fb.h index eafa293..6c4599c 100644 --- a/psplash-fb.h +++ b/psplash-fb.h @@ -22,7 +22,6 @@ typedef struct PSplashFB { intfd; struct

[yocto] [psplash][RFC PATCH 13/14] psplash-drm.c: Allocate resources only for the first connector

Since splash screen is shown only on the first scanout, there is no need to allocate resources for next connectors. Signed-off-by: Vasyl Vavrychuk --- psplash-drm.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/psplash-drm.c b/psplash-drm.c index 2468cf1..5e56286

[yocto] [psplash][RFC PATCH 08/14] psplash.c: Make psplash_draw_{msg,progress} independent of FB

Signed-off-by: Vasyl Vavrychuk --- psplash.c | 64 --- 1 file changed, 33 insertions(+), 31 deletions(-) diff --git a/psplash.c b/psplash.c index 1a5e543..c234d46 100644 --- a/psplash.c +++ b/psplash.c @@ -21,11 +21,11 @@ #endif #include

[yocto] [psplash][RFC PATCH 04/14] Remove 'psplash-fb.h' from 'psplash.h'

psplash might not be necessary based on framebuffer, it could use DRM in future too. Signed-off-by: Vasyl Vavrychuk --- psplash-fb.c | 2 +- psplash-fb.h | 3 +++ psplash.c| 1 + psplash.h| 2 -- 4 files changed, 5 insertions(+), 3 deletions(-) diff --git a/psplash-fb.c b/psplash-fb.c

[yocto] [psplash][RFC PATCH 12/14] Reverse modeset_list

Now, it has the same order as connectors in drmModeGetResources. As result splash screen will be drawn on the first connector. Signed-off-by: Vasyl Vavrychuk --- psplash-drm.c | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/psplash-drm.c b/psplash-drm.c index

[yocto] [psplash][RFC PATCH 06/14] Extract draw rect/image from psplash-fb

Signed-off-by: Vasyl Vavrychuk --- psplash-draw.c | 70 ++ psplash-draw.h | 20 +++ psplash-fb.c | 70 -- psplash-fb.h | 20 --- psplash.c | 16 ++-- 5 files

[yocto] [psplash][RFC PATCH 02/14] Fix 'unused-result' warnings

This fixes warnings such as: ignoring return value of 'chdir', declared with attribute warn_unused_result [-Wunused-result] Signed-off-by: Vasyl Vavrychuk --- psplash-systemd.c | 36 +--- psplash-write.c | 23 ++- psplash.c |

[yocto] [psplash][RFC PATCH 11/14] Implement drm backend

Limitation is that splash screen is drawn only on the first connector. Signed-off-by: Vasyl Vavrychuk --- Makefile.am | 12 +++- configure.ac | 9 +++ psplash-drm.c | 179 +- psplash-drm.h | 17 + psplash.c | 52 +++ 5

[yocto] [psplash][RFC PATCH 01/14] Trim trailing spaces

Signed-off-by: Vasyl Vavrychuk --- psplash-console.c | 34 +++--- psplash-console.h | 8 ++--- psplash-fb.c | 4 +-- psplash-fb.h | 34 +++--- psplash-write.c | 14 - psplash.c | 74 +++

[yocto] [psplash][RFC PATCH 05/14] Extract plot pixel from psplash-fb

psplash_fb_plot_pixel is in fact framebuffer independent. Signed-off-by: Vasyl Vavrychuk --- Makefile.am| 3 +- psplash-draw.c | 120 +++ psplash-draw.h | 51 + psplash-fb.c | 191 +++-- psplash-fb.h

[yocto] [psplash][RFC PATCH 07/14] Extract draw font from psplash-fb

Signed-off-by: Vasyl Vavrychuk --- psplash-draw.c | 109 - psplash-draw.h | 25 psplash-fb.c | 108 psplash-fb.h | 16 psplash.c | 4 +- 5 files changed, 125

Re: [linux-yocto] Build failure drivers/video/fbdev/core/fbmem.c

On 4/25/22 13:23, He Zhe wrote: > Hi Bruce, > > The base context of 2388f826cdc9af2651991adc0feb79de9bdf2232 is removed and > it causes build failure for all branches. if we use linux-yocto 5.15.35 or later. Zhe >