Open-source firmware gets a quarterly release, and the June 2026 edition of coreboot reaches notably far ahead. Coreboot 26.06, released June 25, 2026, adds early support for Intel Nova Lake and AMD Strix Halo — both silicon platforms that haven't hit consumer shelves yet — while welcoming 31 new mainboards to the project's compatibility list.
Intel Nova Lake, Early
Intel engineers contributed early Nova Lake SoC support to the coreboot tree ahead of the platform's commercial debut. It's marked as a work in progress — DDR5 isn't yet supported, and some FSP (Firmware Support Package) workarounds remain while upstream fixes are pending — but having open-source firmware support merged before the chip ships is exactly the kind of ahead-of-time engineering that makes coreboot valuable. Security-sensitive deployments won't need to wait for proprietary firmware to be auditable.
AMD Strix Halo (Ryzen AI Max 300)
AMD's Strix Halo platform — the Ryzen AI Max 300 series — also lands in 26.06. Support currently targets only the AMD Maple reference board, and like the Nova Lake work, it isn't intended for production hardware yet. But Strix Halo is AMD's next-generation integrated graphics architecture with substantial on-chip AI acceleration, and having coreboot support in the tree this early signals a productive upstream relationship between AMD and the coreboot community.
31 New Boards
The board expansion is where most users will find immediate practical value. The 31 newly supported mainboards span a wide range:
- Framework Laptop: additional Framework models join the list, extending the modular laptop's open-source firmware story to more configurations
- ASUS and ASRock: enthusiast-grade desktop boards from both manufacturers, expanding coreboot's reach into mainstream consumer hardware
- Google Chromebooks: several new Google reference devices, which use coreboot as their production firmware
- AMD Crater and AMD Jaguar: AMD reference platforms for embedded and industrial deployments
AMD ROM Armor 2
One of the more significant security improvements in 26.06 is AMD ROM Armor 2 support, which introduces A/B recovery infrastructure for failed firmware loads. When a firmware update goes wrong, the system falls back to the previous known-good image rather than bricking. On embedded and industrial hardware where hands-on recovery isn't always an option, this resilience matters significantly — and it's the kind of feature proprietary UEFI firmware has had in some implementations for years, now arriving in open-source form.
Why Coreboot Still Matters
Proprietary UEFI firmware is effectively unauditable by the people running it. It executes before the operating system, often has network access during initialization, and is implicitly trusted by everything that loads afterward. Coreboot replaces that black box with open, inspectable code that any developer or organization can read, modify, and verify.
The project's quarterly cadence with consistent Intel and AMD engineering contributions suggests coreboot is no longer a niche concern for embedded developers — it's becoming infrastructure for organizations and individuals who take firmware trust seriously. Framework Laptop support in particular means everyday Linux users can run open-source firmware on consumer hardware without buying specialist equipment. That's a meaningful shift in accessibility.