Thank you for the reply. Sorry for the confusion. I am using lib usb
1.0.19. I guess I am on the wrong mailing list. So many flavors of open
source... what is the correct list for lib usb for windows? Can I transfer
the thread or do I need to repost in the correct list?
Bob Tausworthe
On Aug 5,
On Wed, Aug 6, 2014 at 9:08 AM, Bob Tausworthe t...@sentons.com wrote:
Thank you for the reply. Sorry for the confusion. I am using lib usb 1.0.19.
I guess I am on the wrong mailing list. So many flavors of open source...
what is the correct list for lib usb for windows? Can I transfer the
Hi, I had a similar problem a while ago, but my device look-up
strategy was a bit different. My problem was related to a driver bug
that made the Window API report the same hub port for two devices.
This should be impossible and confused libusb, as it assumes that hub
ports are unique. In the end
Hi, it checks the VID and PID
int is_correctdev( libusb_device *dev )
{
struct libusb_device_descriptor desc;
int r = libusb_get_device_descriptor( dev, desc );
//printf(Checking VID=0x%04x, PID=0x%04x\n, desc.idVendor,
desc.idProduct);
if( desc.idVendor == VENDOR_ID
(desc.idProduct
2014-07-29 23:28 GMT+02:00 Bob Tausworthe t...@sentons.com:
Sorry to trouble you but I've exhausted other options. We are developing a
composite HID/debug interace device and are using libusb 1.0 under 32 bit
Cygwin to access the debug interface portion. Everything is working fine on
Windows 7
