libftdi Archives

Subject: Re: Status of async mode

From: Jie Zhang <jie.zhang@xxxxxxxxxx>
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Cc: Daryl Lee <daryl@xxxxxxxxxxxx>
Date: Mon, 27 Jul 2009 20:20:58 +0800
Thomas Jarosch wrote:
Hello Daryl,

On Saturday, 11. July 2009 01:35:28 Daryl Lee wrote:
I am trying to use libftdi in async mode, and have a question about the
status of it, before I spend too much time wandering through the weeds.

Questions:
1.  Is it well-tested?
2.  Is it known to work when the device is opened with
ftdi_usb_open_desc?

Reason for asking:
I'm getting a crash in ftdi_async_complete any time I call it, directly
or indirectly, as in ftdi_usb_close().  The value of ftdi->usb_dev->fd
looks really odd.  I expected something file-descriptor-ish, as a small
integer. I have a very large integer (134607408).  Right now, I'm looking
for the place where that value gets set, but I thought I'd take a moment
to ask for other eyes.  The crash occurs on the call to FD_SET from
inside
_usb_async_cleanup, and the documentation on FD_SET makes it look like it
wants a normal file descriptor.

I guess we (=Intra2net AG) are the only ones using this mode.
So I'd rather call it expermiental-but-works-for-us :-)
No crash known to me so far. Did you find anything out?

I'm working on making UrJTAG using async mode to improve the memory read performance. But the currently libftdi is lack of an async read function.

I'm also trying to make libftdi to use libusb-1.0 API. So we can use the async API provided by libusb-1.0.


Jie


--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
Current Thread