e48351e260
If the daemon either de-duplicates or replaces the object passed emitted from device-added then the object set as the alternate may not be the same instance as the daemon version. This causes weird things to happen. To make this less fragile, specify the *ID* of the object that should be the alternate device, which allows the daemon to do clever things, and then assign the object from the ID as the last step. Although fixing no bug, this makes implementing future functionality easier. |
||
|---|---|---|
| .. | ||
| altos | ||
| amt | ||
| colorhug | ||
| csr | ||
| dell | ||
| dfu | ||
| ebitdo | ||
| nitrokey | ||
| steelseries | ||
| 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.