5079f26f0e
This leads to madness, as some formats are supersets of the detected types, e.g. 'intel-me' is detected as 'quad' and 'bcd' is detected as 'pair'. Where the version format is defined in a specification or hardcoded in the source use a hardcoded enum value, otherwise use a quirk override. Additionally, warn if the version does not match the defined version format |
||
|---|---|---|
| .. | ||
| altos | ||
| amt | ||
| ata | ||
| colorhug | ||
| csr | ||
| dell | ||
| dell-dock | ||
| dell-esrt | ||
| dfu | ||
| ebitdo | ||
| fastboot | ||
| flashrom | ||
| modem-manager | ||
| nitrokey | ||
| nvme | ||
| redfish | ||
| rts54hid | ||
| rts54hub | ||
| steelseries | ||
| superio | ||
| synapticsmst | ||
| test | ||
| thunderbolt | ||
| thunderbolt-power | ||
| udev | ||
| uefi | ||
| unifying | ||
| upower | ||
| wacom-raw | ||
| wacom-usb | ||
| meson.build | ||
| README.md | ||
Adding a new plugin
An extensible architecture allows for providing new plugin types (for reading and writing different firmware) as well as ways quirk their behavior.
You can find more information about the architecture in the developers section of the fwupd website.
If you have a firmware specification and would like to see support in this project, please file an issue and share the spec. Patches are also welcome.
We will not accept plugins that upgrade hardware using a proprietary Linux executable, library, or DBus interface.
Plugin interaction
Some plugins may be able to influence the behavior of other plugins. This includes things like one plugin turning on a device, or providing missing metadata to another plugin.
The ABI for these interactions is defined in: https://github.com/hughsie/fwupd/blob/master/src/fu-device-metadata.h
All interactions between plugins should have the interface defined in that file.