Open michealroberts opened 1 month ago
@krasin Is there a way to call libusb_detach_kernel_driver()
to ensure that we can claim the target interface?
cc @kylelemons Not sure who to ping ...
@krasin Is there a way to call
libusb_detach_kernel_driver()
to ensure that we can claim the target interface?
@michealroberts it's being 11 years since I touched this codebase. Sorry, but my memory returns zero context about it...
@krasin No worries, trying to find the core maintainers for this ... if any are left? :(
Before I review your PR #129, I'd like to see some data to confirm where the issue comes from. Post a result of lsusb -v
for the device in question.
I'm perhaps looking more for advice on what is going wrong, but I am seeing this error:
This is my Connect functionality:
But I am somehow not getting the correct interface numbers from the discovery connection to the device, here is the full debug output:
I think the device can be connected to, it's just that the alternative interface numbers are not matching up ...
When I manually change to this:
I get an index out of range panic ...
I am stumped. Is this a firmware issue?
Let me know what other information is needed, if any ...