On Tuesday, June 29, 2010 15:28:17 Arnim Läuger wrote: > > the current usbblaster driver lists itself as needing libftdi, and it > > includes ftdi headers, but i cant see anywhere in the code where it > > actually calls any ftdi functions. > > The include probably was a remainder of the usbconn restructuring. It's > not required, right. > However, usbblaster.c relies on libftdi to talk to the FT245 device. > These devices add status bytes in the data stream, so libftdi (and > libftd2xx) are required to provide a transparent channel for application > code. > > libftdi/libftd2xx usage is encapsulated in tap/usbconn/libftdi.c and > libftd2xx.c. Both abstract the library-specific calls to the > usbconn-API. While usbconn/libusb.c exhibits the same interface, it > can't talk the FTDI vendor transport protocol. BTW it doesn't implement > usbconn_read and usbconn_write functions.
OK, thanks for the clarification. i'll clean up the dead code and finish up the unification of help that started me down this path in the first place. then i'll add some of your notes here so people like me dont screw it up again in the future ;). -mike
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________ UrJTAG-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/urjtag-development
