usbip-win2: libusb claim_interface = reliable BSoD if WinUSB driver is not installed for the device
I’m using this as a host: https://github.com/jiegec/usbip on Mac (arm64): $ RUST_LOG=debug cargo run --example host
The device I’m working with is super weird. It is exposing 4 interfaces:
interface_number = 0 transfer_type = Interrupt direction = In
interface_number = 1 transfer_type = Bulk direction = Out
interface_number = 1 transfer_type = Bulk direction = In
interface_number = 2 transfer_type = Interrupt direction = In
interface_number = 3 transfer_type = Bulk direction = Out
interface_number = 3 transfer_type = Bulk direction = In
// get device
let mut device_handle = rusb::open_device_with_vid_pid(vendor_id, product_id).unwrap();
let device = device_handle.device();
// configuration
let config_desc = device.config_descriptor(config_index).unwrap();
device_handle.set_active_configuration(config_desc.number()).unwrap();
device_handle.claim_interface(interface_number).unwrap();
device_handle.set_alternate_setting(interface_number, 0).unwrap();
That device_handle.claim_interface(interface_number).unwrap(); line makes it blow up.
Let me know if the logs are right or if what I am doing just isn’t recommended (I can maybe try Windows host -> Windows client if you think it will help)
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 24 (10 by maintainers)
You know what, you are right. They are compiling against Windows SDK 8.1 instead of Windows 10 in the driver.
I don’t think this is it.
If I do Windows host (https://github.com/dorssel/usbipd-win/releases) to your Windows client (usbip-win2) it is working good.
It is when I try to go Android host or Linux host or Mac OS host (which is using libusb and not “Windows driver implementation”) that I run into this issue.
It very well could be “unsupported” but I was looking to figure out why it is unsupported/what is unsupported so I can work around it and fix… 😃
Full windbg output is required