fwupd/plugins/flashrom
Mario Limonciello 75835b4a0b Use FWUPD_COMPILATION define to indicate an in tree build
When this is done, include:
* Including the hash
* Including anything that is not ABI stable in plugins yet

Suggested-by: Simon McVittie <smcv@debian.org>
2021-01-22 14:01:25 -06:00
..
example Fix shebangs on scripts 2019-11-24 18:51:56 -06:00
flashrom.quirk coreboot: Remove plugin and instead add metadata to flashrom devices 2021-01-19 21:32:59 +00:00
fu-flashrom-device.c coreboot: Remove plugin and instead add metadata to flashrom devices 2021-01-19 21:32:59 +00:00
fu-flashrom-device.h coreboot: Remove plugin and instead add metadata to flashrom devices 2021-01-19 21:32:59 +00:00
fu-plugin-flashrom.c Use FWUPD_COMPILATION define to indicate an in tree build 2021-01-22 14:01:25 -06:00
meson.build coreboot: Remove plugin and instead add metadata to flashrom devices 2021-01-19 21:32:59 +00:00
README.md coreboot: Remove plugin and instead add metadata to flashrom devices 2021-01-19 21:32:59 +00:00

Flashrom

Introduction

This plugin uses flashrom to update the system firmware.

Firmware Format

The daemon will decompress the cabinet archive and extract a firmware blob in an unspecified binary file format, which is typically the raw input for an EEPROM programmer.

This plugin supports the following protocol ID:

  • org.flashrom

Coreboot Version String

The coreboot version string can have an optional prefix (see below). After the optional prefix the major, minor string follows and finally the build string, containing the exact commit and repository state, follows.

For example 4.10-989-gc8a4e4b9c5-dirty

Exception on Lenovo devices:

The thinkpad_acpi kernel module requires a specific pattern in the DMI version string. To satisfy those requirements coreboot adds the CBETxxxx prefix to the DMI version string on all Lenovo devices.

For example CBET4000 4.10-989-gc8a4e4b9c5-dirty

The coreboot DMI version string always starts with CBET.

GUID Generation

These device uses hardware ID values which are derived from SMBIOS.

  • HardwareID-3
  • HardwareID-4
  • HardwareID-5
  • HardwareID-6
  • HardwareID-10

These device uses hardware ID values which are derived from SMBIOS. They should match the values provided by fwupdtool hwids or the ComputerHardwareIds.exe Windows utility.

Vendor ID Security

The vendor ID is set from the BIOS vendor, for example DMI:Google

External interface access

This plugin requires access to all interfaces that libflashrom has been compiled for. This typically is /sys/bus/spi but there may be other interfaces as well.