![]() It's actually quite hard to build a front-end for fwupd at the moment as you're never sure when the progress bar is going to zip back to 0% and start all over again. Some plugins go 0..100% for write, others go 0..100% for erase, then again for write, then *again* for verify. By creating a helper object we can easily split up the progress of the specific task, e.g. write_firmware(). We can encode at the plugin level "the erase takes 50% of the time, the write takes 40% and the read takes 10%". This means we can have a progressbar which goes up just once at a consistent speed. |
||
---|---|---|
.. | ||
colorhug.quirk | ||
fu-colorhug-common.c | ||
fu-colorhug-common.h | ||
fu-colorhug-device.c | ||
fu-colorhug-device.h | ||
fu-plugin-colorhug.c | ||
meson.build | ||
README.md |
ColorHug
Introduction
The ColorHug is an affordable open source display colorimeter built by Hughski Limited. The USB device allows you to calibrate your screen for accurate color matching.
ColorHug versions 1 and 2 support a custom HID-based flashing protocol, but version 3 (ColorHug+) has now switched to DFU.
Firmware Format
The daemon will decompress the cabinet archive and extract a firmware blob in a packed binary file format.
This plugin supports the following protocol ID:
- com.hughski.colorhug
GUID Generation
These devices use the standard USB DeviceInstanceId values, e.g.
USB\VID_273F&PID_1001&REV_0001
USB\VID_273F&PID_1001
USB\VID_273F
Update Behavior
The device usually presents in runtime mode, but on detach re-enumerates with a different USB PID in a bootloader mode. On attach the device again re-enumerates back to the runtime mode.
For this reason the REPLUG_MATCH_GUID
internal device flag is used so that
the bootloader and runtime modes are treated as the same device.
Vendor ID Security
The vendor ID is set from the USB vendor, in this instance set to USB:0x273F
External Interface Access
This plugin requires read/write access to /dev/bus/usb
.