mirror of
https://git.proxmox.com/git/fwupd
synced 2025-05-24 16:56:33 +00:00
078beafb2d
It is far too easy to forget to set FWUPD_DEVICE_FLAG_NO_GUID_MATCHING for new
plugins, and without it it all works really well *until* a user has two devices
of the same type installed at the same time and then one 'disappears' for hard
to explain reasons. Typically we only need it for replug anyway!
Explicitly opt-in to this rarely-required behaviour, with the default to just
use the physical and logical IDs. Also document the update behavior for each
plugin to explain why the flag is being used.
This allows you to have two identical Unifying plugged in without one of them
being hidden from the user, at the same time allowing a HIDRAW<->USB transition
when going to and from bootloader and runtime modes.
This removes the workaround added in 99eb3f06b6.
Fixes https://github.com/fwupd/fwupd/issues/2915
69 lines
1.8 KiB
Markdown
69 lines
1.8 KiB
Markdown
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.
|
|
|
|
Update Behavior
|
|
---------------
|
|
|
|
The firmware is deployed to the SPI chip when the machine is in normal runtime
|
|
mode, but it is only used when the device is rebooted.
|
|
|
|
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.
|