511517ad88
Currently we only parse the nvm_version attribute according fwupd expectations when the device is initially added. Elsewhere we just use the raw version as is which might be problematic as the version format can change in the middle (for example "33.02" vs. "33.2"). Fix this so that fu_plugin_thunderbolt_udev_get_version () always returns parsed version string. Update self tests accordingly to have "parsed" version to which we compare against. Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com> |
||
|---|---|---|
| .. | ||
| altos | ||
| amt | ||
| colorhug | ||
| csr | ||
| dell | ||
| dell-esrt | ||
| dfu | ||
| ebitdo | ||
| nitrokey | ||
| redfish | ||
| 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.