Tim, thanks for the reply.
I've removed the call to usb_set_configuration. The Error message went away. Now I am facing another problem. A call to usb_claim_interface returns 0 (meaning call was OK). The next call, after the usb_claim_interface, is a call to usb_control_msg. It returns -110 (aka it fails). What should I do to debug this ? Or, even better, what should I do to make this call pass ? Igor P.S: Reminder: I am running this on a CentOS 6.5 as the __guest__ using VirtualBOX on WIN7 as the host. Running the program on CentOS 6.5 on REAL hardware works flawlessly. ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
