Recent development (unreleased)¶
This document describes the major changes that are expected to be included in the next release of flashrom and which are currently only available by source code checkout (see Building from source). These changes may be further revised before the next release.
Known issues¶
AMD-based PCs with FCH are unable to read flash contents for internal (BIOS flash) chips larger than 16 MB, and attempting to do so may crash the system. Systems with AMD “Promontory” IO extenders (mostly “Zen” desktop platforms) are not currently supported.
flashchips.c split into separate files by vendor¶
flashchips.c file was split into separate files per vendor. flashchips.c still exists in the source
code but it is much smaller and only contain “generic” chip entries.
With this, instead of one file flashchips.c we now have a flashchips/ directory which contains
all the files.
There are no changes to the usage, and everything that’s supported stays the same.
New features¶
-r/-w/-v argument is optional when using -i¶
See Manual page for details.
Hall of Fame added to documentation¶
The flashrom HTML documentation (and web site) now includes an automatically-generated list of historical contributors, to acknowledge everybody who has made flashrom into what it is: Hall of Fame.
When building the documentation, the generate_authors_list Meson option will
cause the lists to be generated, requiring a runnable copy of Git on the system
and that the source tree being built is a Git working copy. If those
requirements are not satisfied or the option is disabled, the authors lists will
be replaced with placeholders unless the generate_authors_list option is set
to enabled in which case the build will fail if the requirements are not
satisfied.
New libflashrom API for progress reporting¶
The old flashrom_set_progress_callback function for requesting progress updates
during library operations is now deprecated. Users should call
flashrom_set_progress_callback_v2 instead, which also changes the signature
of the callback function. Specifically, new function type flashrom_progress_callback_v2
should be used from now on.
This new API fixes limitations with the old one where most users would need to define their own global state to track progress, and it was impossible to fix that issue while maintaining binary compatibility without adding a new API.
Programmer updates¶
spidriver: Add support for the Excamera Labs SPIDriver