-
-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
some hid devices do not work immediately after attaching #54
Comments
You can do almost nothing with linux usbip implementation. Someone should fix this issue and make a pull request. If maintainer of this subsystem approve it, the pull request will be merged into the kernel. I don't like some things in the usbip protocol that complicate client implementation on Windows, but can do nothing with that. |
i also asked this at the developer of usbipd-win project and you can also find some further usbmon captures of the hid device; do you know if this is the right place to address this issue? |
i hope getting more infos here also concerning the linux usbip server implementation. i have similar problems with some hid devices as described here in usbipd-win project, where they fixed the issue with a timeout:
dorssel/usbipd-win#659 (comment)
after attaching the devices, they are shown in a connected state but will not work immediately. only after detaching and reattaching 1 to 3 times then the usb devices come to work correctly. so could this be a similar driver issue in linux server usbip or timeout issue? i would like to also mention that these kind of hid devices mostly have 2 bNumInterfaces and this differs from other devices which normally have only 1 bNumInterfaces and perhaps this could also be the reason. any advice or ideas?
The text was updated successfully, but these errors were encountered: