> It seems clear from the traces that this isn't a problem in libusb.
Agreed. But (a) I needed someone to sanity-check my approach using the
async API, and (b) I knew that you look at this list, and I hoped you might
have some suggestions. And you did!
OK so I tried a few things:
1) Rather than
Hello libusbx-devel,
Firstly, apologies for the long email!
Today I discovered a weird problem with my FPGALink library on my Raspberry
Pi, running Raspbian 2013-09-25 (with the stock armhf/armv6l libusbx-1.0.11
package provided by Raspbian):
$ uname -a
Linux raspberrypi 3.6.11+ #538 PREEMPT Fri
Hi libusbx-devel,
I'd like to write an application which uses the "simple" async approach.
I can't use the polled approach because I'd like my code to be portable
to Windows.
Here's a scenario:
The main thread creates the worker thread, which calls one of the
libusb_handle_events_*() varients in
> As long as your buffering can handle that, you're fine, but it's
> dangerous to make assumptions about bulk throughput...
>
Understood. It's my job as library designer to ensure I do everything I
can to ensure performance is optimal assuming ideal conditions (i.e if
there is slowness anywhere, i
tion" code on both ends of the link agrees to
use packets of 64 bytes or fewer, the "system" code in between needs to
see the EP1IN size reported as 512 bytes.
Thanks again!
Chris
On Thu, 2012-09-06 at 09:55 -0700, Tim Roberts wrote:
> Chris McClelland wrote:
> > Basic
OK, I made more progress with my Windows/Linux discrepancies, and I have
now hit another problem. I haven't totally ruled out the possibility
that it's another FX2 firmware bug, but I have narrowed it down to a
pretty simple example on the host and FX2 side:
http://www.swaton.ukfsn.org/temp/libusb
> While I have to say your code is A LOT cleaner than the fxload one
That's because I'm not very smart - breaking problems down is the only
hope I have of solving them!
> (and at the very least, I'd like to use your firmware with the vendor
> commands for eeprom flashing),
If you want to adopt
OK, it's good to know about the WinUSB set-config limitation. Presumably
the same is true for the set-alt-interface call?
If you're interested, the project I'm porting (from libusb-0.1) is
FPGALink:
http://www.makestuff.eu/wordpress/software/fpgalink/
The performance difference is staggering. Th
Hi libusbx-devel,
Firstly thanks for the lively fork! It's great that libusb is being so
actively developed.
I'm in the process of debugging some host-side code and Cypress FX2LP
firmware. Things work fine on Linux and on MacOSX, but things go awry on
Windows (using WinUSB driver). I coult show y
