dbcc8e1137
Some vendors want to ship updates for ATA hardware, but there are currently no lock-down restrictions in place for these kind of devices. There is the OUI from the WWN block which is supposed to identify the vendor, but this is not always set and so we have to be a little creative. We can match 90% of hardware using the vendor name prefix, and the last 10% can be detected with a heuristic that was the result of comparing over 900 drive models. I'm not including very old drive models, media converters, raid controllers, or external 'portable' drives as I don't think it is useful. Also, if the drive contains a Dell vendor block just hardcode this as Dell rather than trying to be clever. Also ask the user to contribute OUI values if this data is found with no quirk data as this is the only real sane way to manage this data long term. The list of OUIs can be found here: http://standards-oui.ieee.org/oui.txt |
||
|---|---|---|
| .. | ||
| altos | ||
| amt | ||
| ata | ||
| colorhug | ||
| coreboot | ||
| csr | ||
| dell | ||
| dell-dock | ||
| dell-esrt | ||
| dfu | ||
| ebitdo | ||
| emmc | ||
| fastboot | ||
| flashrom | ||
| fresco-pd | ||
| jabra | ||
| logitech-hidpp | ||
| modem-manager | ||
| nitrokey | ||
| nvme | ||
| optionrom | ||
| redfish | ||
| rts54hid | ||
| rts54hub | ||
| solokey | ||
| steelseries | ||
| superio | ||
| synaptics-cxaudio | ||
| synaptics-mst | ||
| synaptics-prometheus | ||
| synaptics-rmi | ||
| test | ||
| thelio-io | ||
| thunderbolt | ||
| thunderbolt-power | ||
| tpm | ||
| tpm-eventlog | ||
| uefi | ||
| uefi-recovery | ||
| upower | ||
| vli | ||
| 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.
You can use the fwupd developer documentation to assist with APIs available to write the plugin.
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, proprietary UEFI executable, proprietary 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/fwupd/fwupd/blob/master/src/fu-device-metadata.h
All interactions between plugins should have the interface defined in that file.