56ac823af9
Some plugins have devices with more than one protocol. Logically the protocol belongs to the device, not the plugin, and in the future we could use this to further check firmware that's about to be deployed. This is also not exported into libfwupd (yet?) as it's remains a debug-feature only -- protocols are not actually required for devices to be added. |
||
|---|---|---|
| .. | ||
| data | ||
| fu-logitech-hidpp-bootloader-nordic.c | ||
| fu-logitech-hidpp-bootloader-nordic.h | ||
| fu-logitech-hidpp-bootloader-texas.c | ||
| fu-logitech-hidpp-bootloader-texas.h | ||
| fu-logitech-hidpp-bootloader.c | ||
| fu-logitech-hidpp-bootloader.h | ||
| fu-logitech-hidpp-common.c | ||
| fu-logitech-hidpp-common.h | ||
| fu-logitech-hidpp-hidpp-msg.c | ||
| fu-logitech-hidpp-hidpp-msg.h | ||
| fu-logitech-hidpp-hidpp.c | ||
| fu-logitech-hidpp-hidpp.h | ||
| fu-logitech-hidpp-peripheral.c | ||
| fu-logitech-hidpp-peripheral.h | ||
| fu-logitech-hidpp-runtime.c | ||
| fu-logitech-hidpp-runtime.h | ||
| fu-logitech-hidpp-self-test.c | ||
| fu-plugin-logitech-hidpp.c | ||
| logitech-hidpp.quirk | ||
| meson.build | ||
| README.md | ||
Logitech HID Support
Introduction
This plugin can flash the firmware on Logitech Unifying dongles, both the Nordic (U0007) device and the Texas Instruments (U0008) version.
This plugin will not work with the different "Nano" dongle (U0010) as it does not use the Unifying protocol.
Some bootloader protocol information was taken from the Mousejack[1] project, specifically logitech-usb-restore.py and unifying.py. Other documentation was supplied by Logitech.
Additional constants were taken from the Solaar[2] project.
Firmware Format
The daemon will decompress the cabinet archive and extract a firmware blob in a vendor-specific format that appears to be a subset of the Intel HEX format.
This plugin supports the following protocol IDs:
- com.logitech.unifying
- com.logitech.unifyingsigned
GUID Generation
These devices use the standard USB DeviceInstanceId values when in DFU mode:
USB\VID_046D&PID_AAAA&REV_0001USB\VID_046D&PID_AAAAUSB\VID_046D
When in runtime mode, the HID raw DeviceInstanceId values are used:
HIDRAW\VEN_046D&DEV_C52BHIDRAW\VEN_046D
Design Notes
When a dongle is detected in bootloader mode we detach the hidraw driver from the kernel and use raw control transfers. This ensures that we don't accidentally corrupt the uploading firmware. For application firmware we use hidraw which means the hardware keeps working while probing, and also allows us to detect paired devices.
[1] https://www.mousejack.com/ [2] https://pwr-Solaar.github.io/Solaar/