The 4.19 release was completed on the 16th of January 2023.
Since the last release, the coreboot project has merged over 1600 commits from over 150 authors. Of those authors, around 25 were first-time committers to the coreboot project.
As always, we are very grateful to all of the contributors for helping to keep the project going. The coreboot project is different from many open source projects in that we need to keep constantly updating the codebase to stay relevant with the latest processors and technologies. It takes constant effort to just stay afloat, let alone improve the codebase. Thank you very much to everyone who has contributed, both in this release and in previous times.
Note that the first set of tarballs posted for the 4.19 release had bad timestamps. This has been fixed. Hashes for all tarballs are at the bottom of this document.
The 4.20 release is planned for the 20th of April, 2023.
The coreboot build system automatically adds a 'config' file to CBFS that lists the exact Kconfig configuration that the image was built with. This is useful to reproduce a build after the fact or to check whether support for a specific feature is enabled in the image.
This file has been generated using the 'savedefconfig' Kconfig command, which generates the minimal .config file that is needed to produce the required config in a coreboot build. This is fine for reproduction, but bad when you want to check if a certain config was enabled, since many options get enabled by default or pulled in through another option's 'select' statement and thus don't show up in the defconfig.
Instead coreboot now includes a larger .config instead. In order to save some space, all of the comments disabling options are removed from the file, except for those included in the defconfig.
We can also LZMA compress the file since it is never read by firmware itself and only intended for later re-extraction via cbfstool, which always has LZMA support included.
Until recently, coreboot still contained lots of code using the legacy ASL syntax. However, all ASL code was ported over to make use of the ASL 2.0 syntax and from this point on new ASL code should make use of it.
Intel Icelake is unmaintained and the only user of this platform ever was the Intel CRB (Customer Reference Board). From the looks of the code, it was never ready for production as only engineering sample CPUIDs are supported.
Intel Icelake code will be removed following 4.19 and any maintenance will be done on the 4.19 branch. This consists of the Intel Icelake SoC and Intel Icelake RVP mainboard.
The SoC Intel Quark is unmaintained and different efforts to revive it failed. Also, the only user of this platform ever was the Galileo board.
Thus, to reduce the maintenance overhead for the community, support for the following components will be removed from the master branch and will be maintained on the release 4.20 branch.
Issues from the coreboot bugtracker: https://ticket.coreboot.org/
+-----+-----------------------------------------------------------------+ | # | Subject | +=====+=================================================================+ | 449 | ThinkPad T440p fail to start, continuous beeping & LED blinking | +-----+-----------------------------------------------------------------+ | 448 | Thinkpad T440P ACPI Battery Value Issues | +-----+-----------------------------------------------------------------+ | 446 | Optiplex 9010 No Post | +-----+-----------------------------------------------------------------+ | 445 | Thinkpad X200 wifi issue | +-----+-----------------------------------------------------------------+ | 439 | Lenovo X201 Turbo Boost not working (stuck on 2,4GHz) | +-----+-----------------------------------------------------------------+ | 427 | x200: Two battery charging issues | +-----+-----------------------------------------------------------------+ | 414 | X9SAE-V: No USB keyboard init on SeaBIOS using Radeon RX 6800XT | +-----+-----------------------------------------------------------------+ | 412 | x230 reboots on suspend | +-----+-----------------------------------------------------------------+ | 393 | T500 restarts rather than waking up from suspend | +-----+-----------------------------------------------------------------+ | 350 | I225 PCIe device not detected on Harcuvar | +-----+-----------------------------------------------------------------+ | 327 | OperationRegion (OPRG, SystemMemory, ASLS, 0x2000) causes BSOD | +-----+-----------------------------------------------------------------+
Old tarballs:
New tarballs: