Framework Computer just took a concrete step toward greater firmware transparency. Last week coreboot gained upstream support for the company’s Meteor Lake-powered Laptop 13. Days later its own downstream repository added initial code for the fresh Panther Lake model now shipping as the Laptop 13 Pro.
The progress matters. For years customers have pressed Framework to move beyond proprietary BIOS. Community threads fill with requests for auditable boot firmware that removes Intel Management Engine dependencies where possible. Now the company itself appears to be investing engineering time. Phoronix reported the developments Monday.
Call it Marigold. That’s the codename merged into coreboot mainline for the Framework Laptop 13 with Intel Core Ultra Series 1, also known as Meteor Lake. Most core functions operate. The eSPI keyboard works. So does the emulated PS/2 touchpad. Battery and AC status report correctly once the embedded controller ACPI tables align. Yet gaps remain. Thunderbolt 4 and USB4 remain untested. Modern standby states need validation. Those details come straight from the commit and accompanying documentation added to the tree.
But Sakura tells a forward-looking story. Framework’s internal coreboot fork gained a new board definition for the Laptop 13 with Intel Core Ultra Series 3 processors. These Panther Lake chips power the just-launched 13 Pro. Functionality mirrors the Meteor Lake port so far. The move shows Framework isn’t waiting for community ports. It’s writing code ahead of broader release.
From Community Pressure to Company Commitment
Framework never hid its modular philosophy. Schematics sit on GitHub. Expansion cards let users swap ports. Memory and storage upgrade without soldering. Yet the boot firmware stayed closed. Earlier community efforts targeted older AMD Ryzen boards. 9elements began porting coreboot plus AMD’s openSIL to the Framework 16 Gen 1 and planned the same for the AMD Framework 13. That work remains early. Memory training and silicon initialization still demand attention. Phoronix covered those AMD efforts in March.
Intel paths proved harder. Meteor Lake introduced new power domains, integrated graphics complexities, and tighter integration with the embedded controller. The upstream merge required coordinated patches across multiple subsystems. Documentation commits spell out exact build instructions and known limitations. No one claims production readiness yet. Still, the code now lives in the open where anyone can inspect, compile, and improve it.
Framework’s downstream addition of Sakura carries extra weight. The company sells the Laptop 13 Pro as its flagship for developers. It ships with Ubuntu preinstalled and certified. Battery tests show 20 hours of 4K Netflix playback under efficient settings. The chassis uses CNC-machined aluminum. Memory arrives as upgradeable LPCAMM2 modules reaching 64GB. Storage hits 8TB of PCIe Gen5. All specs pulled from the official product page at frame.work.
Officials call it “the ultimate developer laptop.” They emphasize repairability, Linux support across distributions, and open design files. Firmware appears in that GitHub repository too, though not yet coreboot by default. The Panther Lake port suggests that could change.
Coreboot itself advanced in parallel. Its 26.03 release in late March delivered full Panther Lake SoC enablement. The project merged 876 commits from 95 contributors. Refinements to runtime configuration options, power management tuning, and security lockdowns accompanied the new silicon support. The official coreboot blog announcement highlighted explicit dependency wiring for Intel platforms and new PCIe and power controls exposed to users.
So the pieces align. Hardware ships with modern Intel silicon. Coreboot adds the matching SoC code. Framework writes board-specific support. Linux distributions already run well on these laptops. The remaining distance to shipping coreboot by default looks shorter than before.
Users care for multiple reasons. Auditable firmware reduces supply-chain risk. Removing or neutralizing management engine code appeals to security-conscious buyers. Faster boot times and lower memory overhead appeal to developers. For a company built on modularity and longevity, open firmware completes the picture.
Plenty of work stays ahead. Thunderbolt validation. Full s0ix residency. Embedded controller integration that doesn’t require binary blobs. Hardware-specific quirks on the new aluminum chassis with its haptic trackpad. Framework has not announced official support timelines. Community forums still debate costs and priorities. One older thread estimated initial ports in the low five figures. Yet job postings once sought coreboot and Tianocore experience. Those listings disappeared. Progress continues anyway.
And the timing feels deliberate. Framework launched the 13 Pro in April to strong reviews. Tom’s Hardware described it as aiming to become a “MacBook Pro for Linux users.” The hardware impresses. Pairing it with fully open boot firmware would sharpen that positioning.
Watch the Gerrit reviews. Follow Framework’s downstream tree. Test the Marigold builds yourself if you own the Meteor Lake model. The code exists. Momentum builds. For an industry that talks transparency but ships binary blobs, Framework’s latest moves stand out as practical delivery.
WebProNews is an iEntry Publication