The common thread this fortnight is tooling and turnaround — the parts of the stack that decide how fast you build, boot, and render. The current Yocto LTS, 6.0 “wrynose”, has dropped its cve-check class in favour of Bootlin’s sbom-cve-check, Linux 7.2-rc2 splits the long-monolithic device-ID headers to cut needless full-tree rebuilds, and a proposed DRM scheduler rework aims to stop compositors dropping frames when the CPU is loaded. On the hardware side, Raspberry Pi added a 10-inch Touch Display 2 at $80.
Yocto’s wrynose LTS replaces the cve-check class with sbom-cve-check, the mod_devicetable header split lands in Linux 7.2-rc2, a proposed DRM scheduler rework to cut GPU submission latency, and a new 10-inch Raspberry Pi Touch Display 2 at $80.
Not every important update is a headline feature. This edition covers four developments that change day-to-day work for embedded teams: the tools you build with, the time your tree takes to rebuild, the smoothness of your on-device UI, and the panels you ship on. None of them is dramatic on its own, but together they shape build times, boot times, and product cost.
In this edition
- Yocto wrynose drops cve-check for sbom-cve-check. The 6.0 LTS has removed the long-standing
cve-checkclass; its replacement,sbom-cve-check, scans both at build time and against an already-built image (Yocto 6.0 migration notes). - Linux 7.2-rc2 splits the device-ID headers. The monolithic
mod_devicetable.his broken into per-subsystem headers to reduce full-tree recompiles (Phoronix, OSTechNix). - A DRM scheduler rework targets GPU submission latency. A proposal replaces workqueues with
kthread_workso a high-priority GPU client is not delayed by a busy CPU (Phoronix). - Raspberry Pi ships a 10-inch Touch Display 2. A 1200×1920 IPS panel with 10-point touch at $80 (Raspberry Pi).
Yocto’s wrynose LTS replaces cve-check with sbom-cve-check
The current Yocto LTS is 6.0 “wrynose”, and its point releases have made a change worth acting on: the cve-check class has been removed and replaced by sbom-cve-check (openembedded-core commit 00de455), a change carried in the current 6.0.2 update. cve-check was the standard way a Yocto build reported unpatched CVEs in an image, so this is not a cosmetic change — it alters how every team tracks vulnerabilities in a wrynose product.
The reasoning, in the maintainers’ own words, is that cve-check “is not that usable in the real world”. sbom-cve-check, written by Bootlin, closes the main gap: it can run both during the build and afterwards, against an already-built image, so you can re-scan a shipped product for newly disclosed CVEs without rebuilding it. That periodic re-scan is what a maintained product actually needs, and it is what the older class could not do. The class was deleted outright rather than carried, so it does not have to be maintained across the four-year wrynose support window.
The migration is small but real. Enabling the new class deploys two reports to DEPLOY_DIR_IMAGE: a .sbom-cve-check.yocto.json file in the same JSON format the old class produced, and a .sbom-cve-check.spdx.json SPDX report annotated with the CVEs found. The plain-text .cve.txt summary is no longer written by default; if your CI parses it, either switch to the JSON or restore the summary explicitly.
SBOM_CVE_CHECK_EXPORT_VARS:append = " SBOM_CVE_CHECK_EXPORT_SUMMARY"Two smaller changes travel with it. CVE_CHECK_SHOW_WARNINGS is gone, replaced by SBOM_CVE_CHECK_SHOW_WARNINGS with the same effect, and CVE_PRODUCT no longer requires special characters to be escaped. If you carry CVE scanning in a wrynose build, act now: rename the warnings variable, point your report parsing at the new JSON, and review your CVE_PRODUCT assignments. The change also lines your CVE evidence up with the SBOM output an EU Cyber Resilience Act audit expects.
Linux 7.2-rc2 splits the device-ID headers
Linux 7.2-rc2 was released on 5 July 2026, and development is on schedule for a stable 7.2 in late August or early September. One structural change in this cycle is a large refactor of the kernel’s device-ID headers: the long-monolithic include/linux/mod_devicetable.h has been broken up into smaller, per-subsystem headers, a change reported across the tree in more than a thousand files (Phoronix, OSTechNix).
The reason this matters is build time. That single header defined the match structures for almost every bus and subsystem, so touching one device ID could force a recompile of a large part of the tree. Splitting it means a change to, for example, a USB ID pulls in only the USB device-ID header, and unrelated subsystems no longer rebuild.
For anyone who compiles the kernel repeatedly — driver developers, BSP maintainers, CI pipelines — this reduces incremental build times, which is where most engineering hours actually go. The effect is invisible in a from-clean build and clear in the edit-compile-test loop.
There is a migration cost for out-of-tree drivers. If your driver includes mod_devicetable.h and relies on structures that now live in a per-subsystem header, you may need to adjust your includes when you rebase onto 7.2. Build your out-of-tree modules against a 7.2 release candidate now rather than discovering the missing include on the day you ship. Do not assume a specific new header path from second-hand coverage; confirm it against the 7.2 source tree when it lands.
A DRM scheduler rework targets GPU submission latency
Tvrtko Ursulin of Igalia sent a request-for-comments series that reworks the DRM GPU scheduler to lower job-submission latency when the system is loaded with many runnable processes (Phoronix, Igalia blog). The problem is that the scheduler currently pushes work through kernel workqueues, so when the CPU run queue is busy a high-priority graphics client can wait behind unrelated CPU work before its commands even reach the GPU.
The proposal replaces the workqueue path with kthread_work, dedicated kernel-thread execution, and the author reports a striking improvement, noting it is directly useful for preventing compositors from missing frames. This is a proposal under review, not a merged feature, so treat it as a direction rather than a shipped change.
For embedded teams this is more relevant than it looks. A product running a Wayland compositor on an SoC GPU — a kiosk, an instrument cluster, an industrial HMI — is exactly the case where a loaded CPU causes visible stutter in the UI. If you ship a graphics-driven interface, measure your frame pacing under deliberate CPU load today so you have a baseline, and follow this series; it points at the mechanism behind a class of stutter that is easy to blame on the GPU driver and hard to reproduce.
Raspberry Pi ships a 10-inch Touch Display 2
Raspberry Pi introduced a 10-inch model of its Touch Display 2 on 22 July 2026 at $80, alongside the existing smaller panels (Raspberry Pi, LinuxGizmos). The 10.1-inch IPS panel runs at 1200×1920, supports ten-point capacitive touch, is rated around 400 cd/m², and connects to the Raspberry Pi 5 and supported Compute Module carriers. The box includes the cables and mounting hardware.
The detail that affects design work is orientation: the panel is native portrait at 1200×1920. If your product is a landscape HMI you will drive it rotated, which means setting the display rotation in your compositor or kernel command line and checking that touch coordinates are transformed to match. A panel that shows the right image but reports touches from the wrong corner is a rotation-transform issue, not a hardware fault.
For product teams, an officially supported panel with documented Raspberry Pi integration lowers the risk that a third-party display carries — no guessing at a DSI timing table, no orphaned vendor patch to carry across kernel upgrades. At $80 with a Compute Module, this is a credible basis for a small production HMI, not only a bench toy. If you have been carrying a custom panel and a fragile out-of-tree display driver, this is worth a cost-and-maintenance comparison against your current bill of materials.
References
- Yocto Project 6.0 migration notes — cve-check class removed — docs.yoctoproject.org
- sbom-cve-check — Bootlin (GitHub)
- Yocto Project 6.0 “wrynose” released with Linux 6.18 LTS — CNX Software
- Linux 7.2-rc2 released — Phoronix
- Linux 7.2-rc2: cleaning up the monster headers — OSTechNix
- DRM scheduler patches for lower job-submission latency — Phoronix
- Fair(er) DRM GPU scheduler — Igalia (Tvrtko Ursulin)
- A new 10-inch Raspberry Pi Touch Display 2 at $80 — Raspberry Pi
- Raspberry Pi launches 10-inch Touch Display 2 — LinuxGizmos
— Raghu Bharadwaj
