Chen
Chen
前来考古
The protocol of USBIP is not well documented, and I only worked this repo towards the implementation of usbip under Linux.
I don't have a windows development environment at hand now, so if you are interested, you are welcome to make this library compatible to usbip-win.
``` when calling '''./usbip attach -r 127.0.0.1 -b 0''' example doesn't detect bus, because usbip-win sends bus id in format like "0\0fefefefefe..." - and you check for "0\0\0\0\0\0\0..." I've fixed...
``` than it doesnt work - and get stuck in loop, reporting wrong packet requests from client. I've found solution for that by manualy replacing: 0x02, // bcdUSB: USB 2.1...
``` And my ultimate goal is to have syncronous api which i can call something like PressKey("A"); ReleaseKey("A"); from thread with logic, imitating human input. ``` This could be done...
``` and self.ep0_in.max_packet_size as u8, // bMaxPacketSize0 with 0x08, // bMaxPacketSize0 ``` If I recall correctly, USB 2.0 and USB1.1 have different constraints on max packet size.
I am not expert on USB, either.
Yes, the original usbip protocol seems unchanged for a long time and operating system support is distributed in different projects e.g. usbip in mainline linux, [usbipd-win](https://github.com/dorssel/usbipd-win) etc.
Why is it redundant?