Nikolai Kondrashov

@whot@fosstodon.org @jose_exposito@fosstodon.org @kernellogger@fosstodon.org I misremembered somewhat. They actually sent me the source code of a little USB device driver (not HID) in 2018, which had a file with installation instructions, but also the description of the protocol in the .c file header (screenshot below). It was somewhat useful as the confirmation and clarification of the actual observed protocol. It's likely out-of-date by now. Not sharing the complete sources, as I don't really know how sensitive they are about it.

@whot@fosstodon.org @jose_exposito@fosstodon.org @kernellogger@fosstodon.org Great work, Jose! I wouldn't attribute VID:PID and name reuse to any kind of forethought, misguided or not, but rather to good ol' Chinese "if it works, ship it!" To complement that, the only docs I ever received from Huion was a few lines in a text file.

@whot@fosstodon.org @jose_exposito@fosstodon.org @kernellogger@fosstodon.org Indeed, that gives me hope too!

@whot@fosstodon.org @jose_exposito@fosstodon.org @kernellogger@fosstodon.org It also occurs to me that the rationale of reusing the VID:PID pairs could be simply avoiding updating the firmware and the driver, which are probably both universal (to an extent). I also wonder if there's any bureaucratic overhead for adding support for a new device from Microsoft's side. This still follows the hacky Chinese approach, of course.