linux/poky.git, branch walnascar-5.2

migration-guides/release-notes-5.2.rst: add missing cves

2025-04-23T18:50:52+00:00

Add missing fixed CVEs to the release note as reported here: https://lore.kernel.org/r/5fc0d33e-4ba5-4f8d-80c2-c5c87be79680@gmail.com Additions can be verified at the following links: - https://gstreamer.freedesktop.org/security/ - https://www.openssh.com/txt/release-9.9p2 - http://www.dest-unreach.org/socat/ libssh2 CVE-2023-48795 was already fixed in previous releases so remove it. See the previous migration guides. Otherwise the CVE entries have been sorted. Reported-by: Takayasu Ito (From yocto-docs rev: b8d9cf79d299b2e553e6bc962527d835206022ec) Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie

migration-guides/release-notes-5.2.rst: fix badly formatted gstreamer entries

2025-04-23T18:50:52+00:00

Reviewed-by: Quentin Schulz (From yocto-docs rev: 22babeaa9ef4c0e6706c6de8f16fbd0e8d505818) Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie

migration-guides/{migration,release-notes}-5.2.rst: notes for systemd pni-names

2025-04-23T18:50:52+00:00

Add a note to the migration guide regarding the pni-names behavior change. Suggested-by: Enrico Jörns (From yocto-docs rev: 9a1b9778c296351a575501a4abc5317e9be954bc) Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie

genericarm64: add ttyPS1 for KV260

2025-04-23T18:49:06+00:00

The AMD KV260 has a serial console on ttyPS1, so until we can dynamically detect the console under sysvinit we can add it to SERIAL_CONSOLES so this platform has a working console when not running systemd. (From meta-yocto rev: 467b6d77e50f92bee3c8f7ca928bd70758bab457) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

systemd: always depend on the explicit serial console units

2025-04-23T18:49:06+00:00

The systemd-serialgetty recipe generates explicit units for consoles that are defined in SERIAL_CONSOLES, and if that variable is not defined then just produces an empty package. Even when systemd has been configured to use the getty generator, if there are explicit consoles defined then we should respect them. Don't conditionalise the dependency on systemd-serialgetty so that we always pull in the explicit consoles. (From OE-Core rev: 6ec2c52b938302b894f119f701ffcf0a847eee85) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

systemd: enable getty generator by default

2025-04-23T18:49:06+00:00

Until recently, even when the getty generator was disabled in the systemd recipe it was actually still active. This was because the old behaviour was to delete the serial-getty template unit if the generator was disabled, but the systemd-serialgetty package shipped then shipped the same files so the generator continued to run. This was a bug in the original commit[1] so this behaviour has been present since 2016. My recent fixes[2] changed this: if the getty generator was disabled then the generator itself is deleted. This makes the actual behaviour match the intention, but the consequence was to demonstrate that some modern platforms were relying on this unexpected behaviour: specifically the genericarm64 BSP which intends to support a number of virtual and physical boards with a number of serial console ports that are not really suitable to be hardcoded into SERIAL_CONSOLES: - ttyS0 - ttyAMA0 (AMBA PL011 uart) - ttyS2 (BeagleBone Play, S0 and S1 are internal) - hvc0 (KVM) - ttyPS1 (AMD KV260) - And most likely more Restore the existing behaviour by explicitly enabling the serial getty generator: this means that systemd will automatically bring up a getty on the first serial console it finds. In the future we should extend some level of dynamic console-finding to sysvinit-based systems by searching for a console device in inittab, but for now this reverts the unintentional regression. [1] oe-core 2a8d0df47c9 ("systemd: make systemd-serialgetty optional") [2] oe-core 2beb3170af6 ("systemd: if getty generator is disabled remove the generator, not the units") (From OE-Core rev: 87136e18b70c0fb66d7268b30e8bc0da9268aa31) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

mesa-demos: fix detection of GLX headers

2025-04-23T18:48:04+00:00

Backport a patch from upstream to fix the build when glx.pc isn't found, but the glx headers are available. As libglvnd is the only provider of glx.pc and by default we build without libglvnd, this is common. This solves the problem where mesa-demo is missing the GLX demos, such as glxgears. [ YOCTO #15825 ] (From OE-Core rev: 466c01cb1ec9ad2a13dc12b5fa7276b9b450266e) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

mesa: remove obsolete deletion of .la files

2025-04-23T18:48:04+00:00

As Mesa is built with Meson now, there's no need to delete the .la files as they're not installed in the first place. (From OE-Core rev: 7cc1288c0121268b02ab26d0b032cee6cb9eacb4) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

linux-yocto/6.12: cfg: fix iommu configuration for -tiny kernel

2025-04-23T18:48:04+00:00

Integrating the following commit(s) to linux-yocto/.: 1/1 [ Author: Bruce Ashfield Email: bruce.ashfield@gmail.com Subject: iommu: add config dependencies Date: Sun, 20 Apr 2025 22:28:21 -0400 commit [cfg/intel.scc: Include iommu.scc for Arrowlake boot support] moves the iommu configuration to a location that is included by more BSPs and kernel types. One of those kernel types is the -tiny kernel, which uses a allnoconfig base. Due to the allnoconfig, there are missing dependencies to allow the desired options to be enabled in the final .config Those missing options throw configuration audit warnings By adding the required dependencies to the fragment, it is now standalone and can be included from anywhere without configuration audit warnings being triggered. Signed-off-by: Bruce Ashfield ] (From OE-Core rev: 795594476c6fabd5391dc35f254de8028f7c47d6) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

linux-yocto/6.12: cfg: Include iommu.scc for Arrowlake boot support

2025-04-23T18:48:04+00:00

Integrating the following commit(s) to linux-yocto/.: 1/1 [ Author: Yogesh Tyagi Email: yogesh.tyagi@intel.com Subject: cfg/intel.scc: Include iommu.scc for Arrowlake boot support Date: Mon, 14 Apr 2025 11:55:45 +0530 Move features/iommu/iommu.scc from bsp/intel-common/intel-corei7-64.scc and bsp/intel-x86/intel-x86.scc to cfg/intel.scc to eliminate redundancy and ensure IOMMU support (CONFIG_INTEL_IOMMU=y, etc.) is enabled for genericx86-64 on Intel Arrowlake, resolving boot issues. This changes is needed in 6.12 as well as master branch. https://bugzilla.yoctoproject.org/show_bug.cgi?id=15802 Signed-off-by: Yogesh Tyagi Signed-off-by: Bruce Ashfield ] (From OE-Core rev: ff91efc2ab25880967b82cc709954d10d62b8cbe) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie