fwupd/plugins/uefi-recovery
Richard Hughes eddaed0c11 Allow specifying more than one VendorID for a device
Asking the user for the UID mapping isn't working very well, as it requires lots
of manual handholding. It also doesn't work very well when the device vendor
does not actually have a PCI ID or if the vendor has split into two entities.

Just use the OUI address as an additional VendorID and match any of the device
IDs against any of the metadata-supplied values.
2021-01-04 22:30:20 +00:00
..
fu-plugin-uefi-recovery.c Allow specifying more than one VendorID for a device 2021-01-04 22:30:20 +00:00
meson.build Convert libfwupdprivate to a shared library libfwupdplugin 2019-11-27 11:32:43 +00:00
README.md Add external interface messages 2020-10-26 12:05:20 -05:00
uefi-recovery.quirk uefi-recovery: Add a plugin to add a fake ESRT entry for device recovery 2019-09-11 12:47:31 +01:00

UEFI Support

Introduction

Some devices have firmware bugs which mean they do not include a valid ESRT table in old firmware versions.

Create a 'fake' UEFI device with the lowest possible version so that it can be updated to a version of firmware which does have an ESRT table.

GUID Generation

All the HwId GUIDs are used for the fake UEFI device, and so should be used in the firmware metadata for releases that should recover the system.

Vendor ID Security

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

External interface access

This plugin requires no extra access.