Accessing new USB device

[mousumih]

Hello - I am able to setup usbip with wsl2. Thank you very much for the information. When I start my device shows up as 1-130 under Windows and so I bind to 1-130 in Windows and also in wsl2. But when I run a certain application, it is flashing the USB device with new firmware that changes it to a new USB-id 1-101. I would like to have Windows and WSL2 side to bind to this interface in addition to 1-130 before running the application, But as 1-101 does not show up first, I cannot do it. Is there something that can be done to bind using a wildcard?

[rpasek]

I made this code quite a while back for dealing with this issue rpasek/WSL2-Linux-Kernel@f367890

This code allows devices that were previously attached to USBIP to automatically attach again. It still means that you will need to bind to the re-enumerated device at least once to get it to work.

[mousumih]

Thank you - will try this out. On Monday, June 15, 2020, 06:45:15 AM PDT, rpasek <notifications@github.com> wrote: I made this code quite a while back for dealing with this issue rpasek/WSL2-Linux-Kernel@f367890 This code allows devices that were previously attached to USBIP to automatically attach again. It still means that you will need to bind to the re-enumerated device at least once to get it to work. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[mousumih]

One more followup question - when the application is flashing the new firmware, the windows side is able to bind to the new usb-id 1-101 but in the wsl side I am getting error "vhci_hcd: valid_args: 284: Failed attach request for unsupported USB speed: super-speed-plus" - if there something in the linux kernel I need to enable to support this?

Thank you

[DonFlymoor]

I have the same error: "Failed attach request for unsupported USB speed: super-speed-plus"