On 2012.06.25 23:45, Pete Batard wrote:
- The only real controversial addon is that "if (!dbg) UNUSED(dbg);" in
libusb_init(), which is only there be OACR insists on wanting that
variable tested no matter what, before exiting the call. I thought about
somehow concealing this farce with a debug st
Continuing with the warnings, trying to get them out of the way once and
for all to proceed to the more important matters that have been
accumulating.
The attached should address the VS Lvl4 and WDK OACR warnings previously
reported. At least they appear to do on my platform.
Note that I'm a
If the transaction should be working the user could try to change how far in the future the isoc transaction is scheduled for. He can do this by changing line 1370 (in 1.0.9) from:frame += 4;toframe += 6; or something similar.-NathanOn Jun 24, 2012, at 08:28 PM, Xiaofan Chen wrote:On Sun, Jun 24,
On Fri, Jun 22, 2012 at 03:36:53PM +0400, Igor Kuzmin wrote:
> Hello!
>
> I'm software engineer at XIMEA (www.ximea.com) responsible for Linux
> support for our products. We're using libusb-1.0 to handle our USB
> cameras, everything works very stable with USB2 controllers, not so
> good with XHCI
On 2012.06.24 01:22, Xiaofan Chen wrote:
> Just found out that Fedora 17 ships with the defact dllwrap with
> their MinGW-w64 based toolchain (32bit and 64bit) and I have the
> exact same problem when cross-building libusbx under Fedora.
OK, then I don't think we have a choice. I just pushed your
Ellis Whitehead wrote:
> I had hoped that I could make some progress by investigating this
> further myself, but wasn't able to figure much out...
> ...
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber0
> bAlter
