![]() It wasn't hugely clear what the platform ID was actually meant to represent. In some cases it was being used like a physical ID, in others it was a logical ID, and in others it was both. In some cases it was even used as a sysfs path. Clear up all the confusion by splitting the platform ID into two parts, an optional *physical* ID to represent the electrical connection, and an optional *logical* ID to disambiguate composite devices with the same physical ID. Also create an explicit sysfs_path getter for FuUdevDevice to make this clear. This allows WAIT_FOR_REPLUG to always work, rather than depending on the order that the GUIDs were added, and that the kernel would always return the same sysfs path (which it doesn't have to do, especially for hidraw devices). |
||
---|---|---|
.. | ||
data | ||
fu-plugin-unifying.c | ||
lu-common.c | ||
lu-common.h | ||
lu-context.c | ||
lu-context.h | ||
lu-device-bootloader-nordic.c | ||
lu-device-bootloader-nordic.h | ||
lu-device-bootloader-texas.c | ||
lu-device-bootloader-texas.h | ||
lu-device-bootloader.c | ||
lu-device-bootloader.h | ||
lu-device-peripheral.c | ||
lu-device-peripheral.h | ||
lu-device-runtime.c | ||
lu-device-runtime.h | ||
lu-device.c | ||
lu-device.h | ||
lu-hidpp-msg.c | ||
lu-hidpp-msg.h | ||
lu-hidpp.h | ||
lu-self-test.c | ||
meson.build | ||
README.md | ||
unifying.quirk |
Unifying 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 infomation 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.
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.
Verification
If you do not have Unifying hardware you can emulate writing firmware using:
unifying-tool write file.hex -v --emulate=bootloader-nordic
This can also be used to produce protocol data to the command line to compare against USB dumps. This plugin should interact with the hardware exactly like the Logitech-provided flashing tool, although only a few devices have been tested.
[1] https://www.mousejack.com/ [2] https://pwr.github.io/Solaar/