mirror of
https://git.proxmox.com/git/fwupd
synced 2025-05-28 07:18:28 +00:00
bd94740404
In fu_plugin_startup we make sure that the FU_HWIDS_KEY_BIOS_VENDOR matches "coreboot", so there's no need to read it again. Remove the call to fu_plugin_get_dmi_value and drop the first call to fu_device_set_vendor as it gets overwritten below. Hardcode the id string for now. Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com> |
||
|---|---|---|
| .. | ||
| fu-coreboot-common.c | ||
| fu-plugin-coreboot.c | ||
| fu-plugin-coreboot.h | ||
| meson.build | ||
| README.md | ||
coreboot
Introduction
Until now only the version detection has been implemented.
System identification
coreboot can be detected the following ways:
- by parsing SMBIOS type 0 vendor string. On coreboot enabled platforms
it's always
coreboot. - by parsing ACPI tables. An ACPI device with the _HID
BOOT0000exists. (This HID has been reserved for coreboot enabled platforms) - by parsing the devicetree. A node under firmware/coreboot with the
compatible id
corebootexists.
coreboot version string
The coreboot version string always starts with CBET.
After the prefix the version, major, minor string follows and finally
the build string, containing the exact commit and repository state, follows.
For example:
CBET4000 4.10-989-gc8a4e4b9c5-dirty
GUID Generation
These device uses hardware ID values which are derived from SMBIOS. The following HWIDs are added on coreboot enabled platforms:
- HardwareID-3
- HardwareID-4
- HardwareID-5
- HardwareID-6
- HardwareID-10
They do match the values provided by fwupdtool hwids or
the ComputerHardwareIds.exe Windows utility.