![]() This allows delaying the activation of Thunderbolt firmware until shutdown/reboot or when the dock is unplugged. This functionality requires features in the kernel: https://lore.kernel.org/linux-usb/20200622143035.25327-1-mario.limonciello@dell.com/T/#t Matrix of cases to support: * Distro Old Linux kernel (doesn't support authenticate on disconnect) - WD19TB: Should have `skips-restart` flag set No flush or activate features called in `thunderbolt` plugin. `dell_dock` plugin will activate at end of composite update - All other devices: Shouldn't have flags set Should authenticate in Thunderbolt plugin. `1 > nvm_authenticate` * Distro New Linux kernel (supports authenticate on disconnect) - WD19TB: Should have `usable-during-update` flag set but not `skips-restart` Should flush image to SPI in `thunderbolt` plugin `2 > nvm_authenticate_on_disconnect` Should configure TBT device for authenticate on disconnect `1 > nvm_authenticate_on_disconnect` `dell_dock` plugin will configure dock for authenticate on disconnect - All other devices: Shouldn't have flags set Should authenticate in `thunderbolt` plugin. `1 > nvm_authenticate` * ChromeOS (supports authenticate on disconnect) - `thunerbolt.conf` will have `DelayedActivation=true`. - WD19TB: Should have `usable-during-update` flag set but not `skips-restart` Should flush image to SPI in `thunderbolt` plugin `2 > nvm_authenticate_on_disconnect` Should configure device for authenticate on disconnect `1 > nvm_authenticate_on_disconnect` `dell_dock` plugin will configure dock for authenticate on disconnect - All other devices: Should have both `usable-during-update` and `skips-restart` set Should flush image to SPI in `thunderbolt` plugin `2 > nvm_authenticate` Will activate upon logout/shutdown/reboot `1 > nvm_authenticate` |
||
---|---|---|
.. | ||
acpi-dmar | ||
acpi-facp | ||
altos | ||
amt | ||
ata | ||
bios | ||
ccgx | ||
colorhug | ||
coreboot | ||
cpu | ||
cros-ec | ||
csr | ||
dell | ||
dell-dock | ||
dell-esrt | ||
dfu | ||
ebitdo | ||
emmc | ||
ep963x | ||
fastboot | ||
flashrom | ||
fresco-pd | ||
iommu | ||
jabra | ||
linux-lockdown | ||
linux-sleep | ||
linux-spi-lpc | ||
linux-swap | ||
linux-tainted | ||
logind | ||
logitech-hidpp | ||
modem-manager | ||
nitrokey | ||
nvme | ||
optionrom | ||
pci-bcr | ||
pci-mei | ||
redfish | ||
rts54hid | ||
rts54hub | ||
solokey | ||
steelseries | ||
superio | ||
synaptics-cxaudio | ||
synaptics-mst | ||
synaptics-prometheus | ||
synaptics-rmi | ||
test | ||
thelio-io | ||
thunderbolt | ||
tpm | ||
tpm-eventlog | ||
uefi | ||
uefi-dbx | ||
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.