On 2012.11.16 20:44, Eric Lundby wrote: > I have attached output from xusb from both the working version (1.0.12) > and the non working version (latest from GIT).
Let's see... HID collections: [ 0.241013] [00000c4c] libusbx: debug [windows_get_device_list] setting composite interface for [2A3]: [ 0.241013] [00000c4c] libusbx: debug [set_composite_interface] interface[1] already set - ignoring HID collection: \\.\HID#VID_046D&PID_C31C&MI_01&COL02#9&3B6DB36F&0&0001 And a filter driver (on a composite device what's more): [ 0.235013] [00000c4c] libusbx: debug [get_api_type] driver(s): USBCCGP [ 0.236013] [00000c4c] libusbx: debug [get_api_type] lower filter driver(s): JMUSBCCGP [ 0.236013] [00000c4c] libusbx: debug [get_api_type] matched driver name against Composite API Add a sprinkle of: [ 0.245014] [00000d6c] libusbx: debug [winusbx_configure_endpoints] failed to set PIPE_TRANSFER_TIMEOUT for control endpoint 03 [ 0.245014] [00000d6c] libusbx: debug [winusbx_configure_endpoints] failed to disable SHORT_PACKET_TERMINATE for endpoint 03 [ 0.245014] [00000d6c] libusbx: debug [winusbx_configure_endpoints] failed to disable IGNORE_SHORT_PACKETS for endpoint 03 [ 0.245014] [00000d6c] libusbx: debug [winusbx_configure_endpoints] failed to enable ALLOW_PARTIAL_READS for endpoint 03 [ 0.245014] [00000d6c] libusbx: debug [winusbx_configure_endpoints] failed to enable AUTO_CLEAR_STALL for endpoint 03 [ 0.245014] [00000d6c] libusbx: debug [winusbx_configure_endpoints] failed to set PIPE_TRANSFER_TIMEOUT for control endpoint 83 [ 0.245014] [00000d6c] libusbx: debug [winusbx_configure_endpoints] failed to disable SHORT_PACKET_TERMINATE for endpoint 83 [ 0.245014] [00000d6c] libusbx: debug [winusbx_configure_endpoints] failed to disable IGNORE_SHORT_PACKETS for endpoint 83 [ 0.245014] [00000d6c] libusbx: debug [winusbx_configure_endpoints] failed to enable ALLOW_PARTIAL_READS for endpoint 83 [ 0.245014] [00000d6c] libusbx: debug [winusbx_configure_endpoints] failed to enable AUTO_CLEAR_STALL for endpoint 83 You really don't want to make it easy on us, do you? Well, IIRC we have a longstanding issue that I never got a chance to even start looking into when it comes to filter drivers, though it might be limited to the libusb-win32 one. At the very least, could you try to at least remove the filter driver from your machine? Not too sure what to make of the configure endpoint issues. Though I don't think it should cause an issue, you wouldn't happen to have the libusbK DLL installed in system32/sysWOW64 by any chance? Do your reproduce the same issue on a different machine? If possible (you say "custom" - does that mean you control the firmware?), you may also want to try to remove the collection and composite aspect of your HID device, then add them again and see at which point it begins to fail. Finally, I don't see libusb_claim_interface failing in the 1.0.14 log of xusb. If anything xusb was able to claim an interface and query the device strings. Regards, /Pete ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
