2dd731b2f0
This allows a frontend to call update on an individual device ID which will cause a CAB file to be downloaded, but then also re-use the same CAB file to try to process devices with a relationship as part of a transaction. |
||
|---|---|---|
| .. | ||
| altos | ||
| amt | ||
| colorhug | ||
| csr | ||
| dell | ||
| dell-esrt | ||
| dfu | ||
| ebitdo | ||
| flashrom | ||
| nitrokey | ||
| nvme | ||
| redfish | ||
| rts54hid | ||
| rts54hub | ||
| steelseries | ||
| superio | ||
| synapticsmst | ||
| test | ||
| thunderbolt | ||
| thunderbolt-power | ||
| udev | ||
| uefi | ||
| unifying | ||
| upower | ||
| wacomhid | ||
| 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.
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.