mirror of
https://git.proxmox.com/git/fwupd
synced 2025-08-06 14:32:56 +00:00
![]() 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). |
||
---|---|---|
.. | ||
fu-plugin-wacomhid.c | ||
fu-self-test.c | ||
fu-wac-common.c | ||
fu-wac-common.h | ||
fu-wac-device.c | ||
fu-wac-device.h | ||
fu-wac-firmware.c | ||
fu-wac-firmware.h | ||
fu-wac-module-bluetooth.c | ||
fu-wac-module-bluetooth.h | ||
fu-wac-module-touch.c | ||
fu-wac-module-touch.h | ||
fu-wac-module.c | ||
fu-wac-module.h | ||
meson.build | ||
README.md | ||
wacomhid.quirk |
Wacom HID Support
Introduction
Wacom provides interactive pen displays, pen tablets, and styluses to equip and inspire everyone make the world a more creative place.
From 2016 Wacom has been using a HID-based proprietary flashing algorithm which has been documented by support team at Wacom and provided under NDA under the understanding it would be used to build a plugin under a LGPLv2+ licence.
Wacom devices are actually composite devices, with the main ARM CPU being programmed using a more complicated erase, write, verify algorithm based on a historical update protocol. The "sub-module" devices use a newer protocol, again based on HID, but are handled differently depending on thier type.