Tags: Licanux/usbip-win
Tags
new vhci driver based on kmdf UDE The old WDM-based vhci could not fully support USB libraries and applications such as cezanne#111 because it did not implement many USB host contoller & hub functionalities. They were impossible to be properly developed with poor MS documents. However, MS has already implemented most things via USB device emulation(UDE). Now, usbip-win provides a vhci driver using UDE. It is experimental and more tests are required.
vhci driver version up from 0.3 to 0.4 From 103ebb8, vhci drver implementation is quite different from previous drviers, which can simulate a real host controller and a USB hub. So, in order to prevent confusion with an old vhci driver, version up to 0.4 would be helpful.
remove invalid error logs generated by an usbipd while listing devices When an usipd lists exported devices, invalid error logs are generated. (reported from cezanne#137) To suppress unnecessary logs, a stub traversing routine first checks a traversed device has a stub device interface.
Add nominal support of USBDI V3 for vhci controller An ASUS bluetooth USB dongle requires vhci to support USBDI V3. Although the effect of the version up of USBDI cannot be identified, its skeleton is embodied for future implementation. IRP_MN_QUERY_PNP_DEVICE_STATE is also simply implemented to return STATUS_SUCCESS.
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 <hunterize@hotmail.com> 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 <cezanne@codemayo.com> 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 <hunterize@hotmail.com> Date: Fri Aug 16 16:07:51 2019 +0800 fix for compatible id of one interface 0 class device commit 5e41d45 Author: Rex Han <rex.han@razer.com> Date: Mon Aug 12 10:51:54 2019 +0800 fix wrong protocol for getting configuration descriptor
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)
PreviousNext