![]() This allows us to 'nest' firmware formats, and removes a ton of duplication. The aim here is to deprecate FuFirmwareImage -- it's almost always acting as a 'child' FuFirmware instance, and even copies most of the vfuncs to allow custom types. If I'm struggling to work out what should be a FuFirmware and what should be a FuFirmwareImage then a plugin author has no hope. For simple payloads we were adding bytes into an image and then the image into a firmware. This gets really messy when most plugins are treating the FuFirmware *as* the binary firmware file. The GBytes saved in the FuFirmware would be considered the payload with the aim of not using FuFirmwareImage in the single-image case. |
||
---|---|---|
.. | ||
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 Support
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
.