Saving the quirks in the GResource section worked well, but it made the build system very complicated and also meant the .data section was duplicated in both `fwupd` and `fwupdtool` -- negating a lot of the hard-fought savings. Simplify this feature so that we just `cat` all the quirk files together, then gzip them into a single file. This means that at startup fwupd only needs to check the mtime of one file, and weirdly it's actually faster to load a smaller compressed file from disk that it is to load multiple uncompressed files. |
||
|---|---|---|
| .. | ||
| cfu.quirk | ||
| fu-cfu-device.c | ||
| fu-cfu-device.h | ||
| fu-cfu-module.c | ||
| fu-cfu-module.h | ||
| fu-plugin-cfu.c | ||
| meson.build | ||
| README.md | ||
Component Firmware update
Introduction
CFU is a protocol from Microsoft to make it easy to install firmware on HID devices.
This protocol is unique in that it requires has a pre-download phase before sending the firmware to the microcontroller. This is so the device can check if the firmware is required and compatible. CFU also requires devices to be able to transfer the entire new transfer mode in runtime mode.
See https://docs.microsoft.com/en-us/windows-hardware/drivers/cfu/cfu-specification for more details.
This plugin supports the following protocol ID:
- com.microsoft.cfu
GUID Generation
These devices use standard USB DeviceInstanceId values, as well as two extra for the component ID and the bank, e.g.
HIDRAW\VEN_17EF&DEV_7226&CID_01&BANK_1HIDRAW\VEN_17EF&DEV_7226&CID_01HIDRAW\VEN_17EF&DEV_7226
Update Behavior
The device has to support runtime updates and does not have a detach-into-bootloader mode -- but after the install has completed the device still has to reboot into the new firmware.
Vendor ID Security
The vendor ID is set from the USB vendor, in this instance set to HIDRAW:0x17EF
External Interface Access
This plugin requires read/write access to /dev/bus/usb.