[linux-yocto][linux-yocto v6.6/standard/nxp-sdk-6.6/nxp-soc & v6.6/standard/preempt-rt/nxp-sdk-6.6/nxp-soc][PATCH 6/6] Revert "arm64: dts: imx8-ss-lsio: fix pwm lpcg indices"

This reverts commit e9e44fc88abadc52ca6b0f1f8307e6967ddbec22. The clock driver clk-imx8qxp-lpcg still uses LPCG bit-offset instead of clock-indices for clock-controller dts properties, so it can not switch to use lpcg indices. Signed-off-by: Xulin Sun ---

[linux-yocto][linux-yocto v6.6/standard/nxp-sdk-6.6/nxp-soc & v6.6/standard/preempt-rt/nxp-sdk-6.6/nxp-soc][PATCH 5/6] Revert "arm64: dts: imx8qm-ss-dma: fix can lpcg indices"

This reverts commit 20ceb2b50fd5a59825daba5fb82021768afe9f71. The clock driver clk-imx8qxp-lpcg still uses LPCG bit-offset instead of clock-indices for clock-controller dts properties, so it can not switch to use lpcg indices. Signed-off-by: Xulin Sun ---

[linux-yocto][linux-yocto v6.6/standard/nxp-sdk-6.6/nxp-soc & v6.6/standard/preempt-rt/nxp-sdk-6.6/nxp-soc][PATCH 4/6] Revert "arm64: dts: imx8-ss-dma: fix can lpcg indices"

This reverts commit 19a8492473b0afe7340fcf6b764d1c22b8f21ae3. The clock driver clk-imx8qxp-lpcg still uses LPCG bit-offset instead of clock-indices for clock-controller dts properties, so it can not switch to use lpcg indices. Signed-off-by: Xulin Sun ---

[linux-yocto][linux-yocto v6.6/standard/nxp-sdk-6.6/nxp-soc & v6.6/standard/preempt-rt/nxp-sdk-6.6/nxp-soc][PATCH 1/6] Revert "arm64: dts: imx8-ss-conn: fix usb lpcg indices"

This reverts commit 16c2dd96e479440306eee96932400739a0930611. The clock driver clk-imx8qxp-lpcg still uses LPCG bit-offset instead of clock-indices for clock-controller dts properties, so it can not switch to use lpcg indices. Signed-off-by: Xulin Sun ---

[linux-yocto][linux-yocto v6.6/standard/nxp-sdk-6.6/nxp-soc & v6.6/standard/preempt-rt/nxp-sdk-6.6/nxp-soc][PATCH 3/6] Revert "arm64: dts: imx8-ss-dma: fix adc lpcg indices"

This reverts commit 7c4285471c03f9d873421598e2878a99c41def9f. The clock driver clk-imx8qxp-lpcg still uses LPCG bit-offset instead of clock-indices for clock-controller dts properties, so it can not switch to use lpcg indices. Signed-off-by: Xulin Sun ---

[linux-yocto][linux-yocto v6.6][PATCH 0/6]: nxp-soc: Revert " * lpcg indices"

Hi Bruce, This patch series is to revert " * lpcg indices". Please help me merge these into the following two branches: v6.6/standard/nxp-sdk-6.6/nxp-soc v6.6/standard/preempt-rt/nxp-sdk-6.6/nxp-soc arch/arm64/boot/dts/freescale/imx8-ss-conn.dtsi | 4 ++--

[linux-yocto][linux-yocto v6.6/standard/nxp-sdk-6.6/nxp-soc & v6.6/standard/preempt-rt/nxp-sdk-6.6/nxp-soc][PATCH 2/6] Revert "arm64: dts: imx8-ss-dma: fix spi lpcg indices"

This reverts commit a156f37b8e3ca7afbccb3f1b6507e150a20ac892. The clock driver clk-imx8qxp-lpcg still uses LPCG bit-offset instead of clock-indices for clock-controller dts properties, so it can not switch to use lpcg indices. Signed-off-by: Xulin Sun ---

[linux-yocto] [yocto-kernel-cache][yocto-6.6][PATCH] bsp: add new bsp amd-zynqmp

From: Quanyang Wang Add support for amd-zynqmp bsp with standard and preempt-rt kernel. Signed-off-by: Quanyang Wang --- Hi Bruce, Would you please help merge this patch to the branch: yocto-6.6 Thanks, Quanyang --- bsp/amd-zynqmp/amd-zynqmp-preempt-rt.scc | 8 +

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

All, YP M+ or high bugs which moved to a new milestone in WW23 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 14622 bsps-hw.bsps-hw.Test_Seek_bar_and_volume_control manual test case failure

[yocto] Enhancements/Bugs closed WW23!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count randy.macl...@windriver.com 7 mhalst...@linuxfoundation.org 1 Grand Total 8 Thanks, *Stephen K. Jolley* *Yocto Project Program Manager* (*Cell*:(208) 244-4460 * *Email*:

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

All, Below is the list of top 39 bug owners as of the end of WW23 who have open medium or higher bugs and enhancements against YP 5.1. There are 95 possible work days left until the final release candidates for YP 5.1 needs to be released. Who Count ross.bur...@arm.com 39 bruce.ashfi...@gmail.com

Re: [yocto] Kernel mainline recipe does produce lot of warnings

I wouldn't call it convention, it's what you set in your local.conf, fixing the PREFERRED_VERSION to match would work as well. On Mon, Jun 10, 2024 at 6:52 PM Zoran Stojsavljevic wrote: > > Interesting convention! > > Thank you, > Zee > ___ > > On Mon, Jun 10, 2024 at 6:35 PM Martin Jansa

Re: [yocto] Kernel mainline recipe does produce lot of warnings

Interesting convention! Thank you, Zee ___ On Mon, Jun 10, 2024 at 6:35 PM Martin Jansa wrote: > > > What am I missing here??? > > dot after 6.10 in the PV to match your PREFERRED_VERSION. > > On Mon, Jun 10, 2024 at 6:32 PM Zoran via lists.yoctoproject.org > wrote: > > > > Hello Yocto

Re: [yocto] Kernel mainline recipe does produce lot of warnings

> What am I missing here??? dot after 6.10 in the PV to match your PREFERRED_VERSION. On Mon, Jun 10, 2024 at 6:32 PM Zoran via lists.yoctoproject.org wrote: > > Hello Yocto Community, > > I decided to expand a bit my knowledge about mainline kernels. So for > the last few days I have been

[yocto] Kernel mainline recipe does produce lot of warnings

Hello Yocto Community, I decided to expand a bit my knowledge about mainline kernels. So for the last few days I have been trying to make a 6.10-rc2 kernel to work with YOCTO. Somehow I did it, but I got tons of warnings, which I could not figure out why this really happens. Here is how ny

Re: [yocto] [meta-security][PATCH 2/2] mmap-smack-test, smack-test, tcp-smack-test, udp-smack-test: don't use S = ${WORKDIR}

gentle ping On Thu, May 23, 2024 at 7:53 AM Martin Jansa via lists.yoctoproject.org wrote: > > * fixes: > Parsing recipes... > ERROR: meta-security/recipes-mac/smack/mmap-smack-test_1.0.bb: Using S = > ${WORKDIR} is no longer supported > ERROR:

Re: [yocto] [meta-security][PATCH 1/2] {tcp,udp}-smack-test: fix implicit-function-declaration issues fatal with gcc-14

gentle ping On Thu, May 23, 2024 at 7:52 AM Martin Jansa via lists.yoctoproject.org wrote: > > tcp-smack-test: > http://errors.yoctoproject.org/Errors/Details/766925/ > tcp_client.c:55:16: error: implicit declaration of function 'atoi' > [-Wimplicit-function-declaration] > > udp-client-tests:

Re: [yocto] depoly-ipks are missing the lib**.so file for shared library yocto recipe #kirkstone #yocto

On 10 Jun 2024, at 11:26, Altous, Salahaldeen via lists.yoctoproject.org wrote: > > Hi All, > > I have one yocto recipe which inherit meson as build system and generate the > right libs in the image folder > > ├── liblc_core.so -> liblc_core.so.0 > ├── liblc_core.so.0 -> liblc_core.so.0.4.7

[yocto] depoly-ipks are missing the lib**.so file for shared library yocto recipe #kirkstone #yocto

Hi All, I have one yocto recipe which inherit meson as build system and generate the right libs in the image folder ├── liblc_core.so -> liblc_core.so.0 ├── liblc_core.so.0 -> liblc_core.so.0.4.7 └── liblc_core.so.0.4.7 but in the deploy-ipks the .so symbolic link is missing drwxr-xr-x

Re: [yocto] how to fix "QA Issue: Missing Upstream-Status in patch "

On Mon, 10 Jun 2024 at 08:47, emailaddress.ashish via lists.yoctoproject.org wrote: > 2) Whats the suggested / proper way of adding such patches > one way way i create the fix manually and keep them in our custom layer ? > or > is there any other way to handle patches which are