Tags: xiaolou86/usbip-win
Tags
Let VHCI handle a zero class device with multi interfaces as a composite In order to avoid complex merge histories, this commit is manually squashed with followings commits. commit 3ffc9c1 Merge: fea88db c8e5944 Author: unknown <[email protected]> Date: Thu Sep 5 18:28:26 2019 +0800 fix compatible id for only one interface of zero class device commit c8e5944 Author: KyungWoon Cho <[email protected]> Date: Thu Aug 15 20:42:09 2019 +0900 Let VHCI handle a zero class device with multi interfaces as a composite For zero class device(defined at interface level), a userland usbip had fetched class/subclass/protocol information from a first interface via usbip session. @hunterize from cezanne#62 pointed out that only the first interface was detected and created a patch which do not modify a USB class/subclass/protocol. From the his/her idea, a zero class USB device with multiple interfaces will be detected as a composite device. commit fea88db Author: unknown <[email protected]> Date: Fri Aug 16 16:07:51 2019 +0800 fix for compatible id of one interface 0 class device commit 5e41d45 Author: Rex Han <[email protected]> Date: Mon Aug 12 10:51:54 2019 +0800 fix wrong protocol for getting configuration descriptor
return stall pid to host and forward reset_pipe_request to device Followings are commit logs by [email protected]. This work is slightly modified to beautify and remove unused code. This commit may have a fix for multi configurations device problem.
vhci, let a webcam with IAD be detected as COMPOSITE A device with IAD(such as MS LifeCam) can be detected correctly by replying USB/COMPOSITE as a compatible ID. But it's still not working.(Camera app generates an error.) Code beautify progressed - "SerialNo" and "addr" are integrated into "port" - Introduce wudev(windows specific structure for usbip userspace udev)
vhci, fix urb selection error Old vhci does not seem to handle a sort of USB camera. When MS lifecam studio had been tested, usb configuration selection failed. This was due to that the number of interface information in _URB_SELECT_CONFIGURATION does not match with the number in configuration descriptor.