On 2012.10.03 11:42, Ramon Zambelli wrote: > [ 0.203012] [000017f0] libusbx: debug [get_api_type] upper filter > driver(s): libusb0 > [ 0.203012] [000017f0] libusbx: debug [get_api_type] matched driver name > against WinUSB API
Using the libusb-win32 filter driver on top of WinUSB is knwon not to work with the *EXPERIMENTAL* support for the libusb-win32 and libusbK drivers that was introduced with 1.0.1[3|4]. This will typically result in a "could not access configuration descriptor (dummy)" error, which we've actually seen reported on this list less than 2 months ago if I'm not mistaken. Please uninstall the filter driver and try again. Regards, /Pete ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
