-
<P>I haven't experienced too many problems using multiple devices with one thread per device. You do have to watch out for <pre>usb\_find\_busses()</pre> and <pre>usb\_find\_devices()</pre> because they update global data.</P>.
2009-10-29 11:11:07 UTC in libusb-win32
-
You may find it useful to add a device interface GUID via the INF so you call use RegisterDeviceNotification ( http://msdn.microsoft.com/en-us/library/aa363431%28VS.85%29.aspx ) in your software to receive device (interface) arrival notifications.
In your INF in the section [LIBUSB_DEV.AddReg.HW] along with your SupriseRemoveOk flag add the following with your own randomly generated GUID...
2009-10-07 13:01:10 UTC in libusb-win32
-
There is a race condition in add_device after IoAttachDeviceToDeviceStack(). If an IRP arrives before the device object "dev" is actually setup then a bad pointer is dereferenced. This patch rearranges the initialization of of the device object.
2009-10-06 16:43:23 UTC in libusb-win32
-
The comment was corrected in July 2009 in SVN revision 162 and released as v0.1.12.2. Thanks, Stephan!
2009-10-06 09:38:48 UTC in libusb-win32
-
The USB standard says 5 meters.
http://www.usb.org/about/faq/ans5.
2009-08-07 12:55:27 UTC in libusb-win32
-
> I can't claim interface for the second device handle either.
That's good! Otherwise how would the system arbitrate two, or more, applications writing to the same interface at the same time? And what would the multiple applications receive when they request a read?
To allow simultaneous access to the same interface you probably want to write a service and use some kind of IPC with...
2009-06-05 08:17:16 UTC in libusb-win32
-
Maybe check the interface exists in the device config descriptors:
device->descriptor.bNumConfigurations
device->config[yourusbconfiguration].bNumInterfaces
where device is of type "struct usb_device *".
2009-04-09 09:56:54 UTC in libusb-win32
-
That will depend on your USB device's configuration.
2009-03-24 09:23:37 UTC in libusb-win32
-
"ep" means End Point.
2009-03-24 09:06:39 UTC in libusb-win32
-
"The manufacturer has provided the driver and I install their drivers"
In this case you cannot use libusb because the manufacturer's driver will have claimed the interface and should be presenting it as a serial port. You do not need libusb. Open the serial port with hyperterminal, or other user mode application, and send the AT commands.
Regards,
Tim.
2009-01-06 11:52:58 UTC in libusb-win32
