fwupd/plugins/logitech-hidpp
Mario Limonciello ddfc72db56 logitech_hidpp: Ignore detach failures (Fixes: #1183)
Some logitech devices seem to reboot immediately and the failures then
look like a broken pipe, but are actually the device rebooting.

If the device really did fail to detach after the timeout is done we'll
see a message that the device failed to come back instead.
2020-02-11 14:14:51 +00:00
..
data Rename unifying plugin to logitech-hidpp (Fixes: #1329) 2019-11-04 13:35:36 -06:00
fu-logitech-hidpp-bootloader-nordic.c Rename unifying plugin to logitech-hidpp (Fixes: #1329) 2019-11-04 13:35:36 -06:00
fu-logitech-hidpp-bootloader-nordic.h Rename unifying plugin to logitech-hidpp (Fixes: #1329) 2019-11-04 13:35:36 -06:00
fu-logitech-hidpp-bootloader-texas.c Rename unifying plugin to logitech-hidpp (Fixes: #1329) 2019-11-04 13:35:36 -06:00
fu-logitech-hidpp-bootloader-texas.h Rename unifying plugin to logitech-hidpp (Fixes: #1329) 2019-11-04 13:35:36 -06:00
fu-logitech-hidpp-bootloader.c trivial: Fix up some typos found using codespell 2020-01-14 12:25:41 +00:00
fu-logitech-hidpp-bootloader.h Rename unifying plugin to logitech-hidpp (Fixes: #1329) 2019-11-04 13:35:36 -06:00
fu-logitech-hidpp-common.c trivial: Allow compiling without <errno.h> 2019-11-23 17:07:53 +00:00
fu-logitech-hidpp-common.h Rename unifying plugin to logitech-hidpp (Fixes: #1329) 2019-11-04 13:35:36 -06:00
fu-logitech-hidpp-hidpp-msg.c Rename unifying plugin to logitech-hidpp (Fixes: #1329) 2019-11-04 13:35:36 -06:00
fu-logitech-hidpp-hidpp-msg.h Rename unifying plugin to logitech-hidpp (Fixes: #1329) 2019-11-04 13:35:36 -06:00
fu-logitech-hidpp-hidpp.c logitech_hidpp: When detaching to bootloader use non-blocking IO and wait for timeout 2020-02-11 14:14:51 +00:00
fu-logitech-hidpp-hidpp.h Rename unifying plugin to logitech-hidpp (Fixes: #1329) 2019-11-04 13:35:36 -06:00
fu-logitech-hidpp-peripheral.c Set the protocol per-device not per-plugin 2019-11-25 18:01:54 +00:00
fu-logitech-hidpp-peripheral.h Rename unifying plugin to logitech-hidpp (Fixes: #1329) 2019-11-04 13:35:36 -06:00
fu-logitech-hidpp-runtime.c logitech_hidpp: Ignore detach failures (Fixes: #1183) 2020-02-11 14:14:51 +00:00
fu-logitech-hidpp-runtime.h Rename unifying plugin to logitech-hidpp (Fixes: #1329) 2019-11-04 13:35:36 -06:00
fu-logitech-hidpp-self-test.c Rename unifying plugin to logitech-hidpp (Fixes: #1329) 2019-11-04 13:35:36 -06:00
fu-plugin-logitech-hidpp.c Set the protocol per-device not per-plugin 2019-11-25 18:01:54 +00:00
logitech-hidpp.quirk Rename unifying plugin to logitech-hidpp (Fixes: #1329) 2019-11-04 13:35:36 -06:00
meson.build Convert libfwupdprivate to a shared library libfwupdplugin 2019-11-27 11:32:43 +00:00
README.md trivial: Document the use of vendor-id in each plugin 2019-12-11 18:10:44 +00:00

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_0001
  • USB\VID_046D&PID_AAAA
  • USB\VID_046D

When in runtime mode, the HID raw DeviceInstanceId values are used:

  • HIDRAW\VEN_046D&DEV_C52B
  • HIDRAW\VEN_046D

Vendor ID Security

The vendor ID is set from the vendor ID, in this instance set to USB:0x046D in bootloader and HIDRAW:0x046D in runtime mode.

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/