Nikolai Kondrashov

@spbnick@bitbang.social

Open on bitbang.social

Computer nerd, electronics enthusiast. Recovering perfectionist.

Working on Linux Kernel CI at Red Hat, LF KernelCI, and at large.

0 Followers

0 Following

4 Posts

Joined November 26, 2023

GitHub:

https://github.com/spbnick

Blog:

https://spbnick.github.io/

YouTube:

https://www.youtube.com/spbnick

Posts

Open post

Nikolai Kondrashov @spbnick@bitbang.social · May 14, 2024

Nikolai Kondrashov

@spbnick@bitbang.social

Computer nerd, electronics enthusiast. Recovering perfectionist. Working on Linux Kernel CI at Red Hat, LF KernelCI, and at large.

bitbang.social

Replying to @whot@fosstodon.org

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

Open post

Nikolai Kondrashov @spbnick@bitbang.social · May 13, 2024

Nikolai Kondrashov

@spbnick@bitbang.social

Computer nerd, electronics enthusiast. Recovering perfectionist. Working on Linux Kernel CI at Red Hat, LF KernelCI, and at large.

bitbang.social

Replying to @spbnick@bitbang.social

@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.

Open post

Nikolai Kondrashov @spbnick@bitbang.social · May 13, 2024

Nikolai Kondrashov

@spbnick@bitbang.social

Computer nerd, electronics enthusiast. Recovering perfectionist. Working on Linux Kernel CI at Red Hat, LF KernelCI, and at large.

bitbang.social

Replying to @whot@fosstodon.org

@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.

Open post

Nikolai Kondrashov @spbnick@bitbang.social · May 09, 2024

Nikolai Kondrashov

@spbnick@bitbang.social

Computer nerd, electronics enthusiast. Recovering perfectionist. Working on Linux Kernel CI at Red Hat, LF KernelCI, and at large.

bitbang.social

Replying to @whot@fosstodon.org

@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.

Remote instance

bitbang.social

Open on original server