From: Arnim L. <arn...@gm...> - 2007-11-18 09:26:37
|
Hi, The FTDI parport driver currently uses libftdi to talk to the chips. This is an open source library which exhibits a comparable interface as the proprietary libftd2xx (D2XX) by Future Tech. D2XX is available for a variety of operating systems while libftdi in itself is system independent but requires libusb for actual USB system communication. Having support for both libraries would broaden the usability of UrJTAG with FTDI pods. The OpenOCD project demonstrates this dual support in its interfacing code where equivalent function calls to libftdi and libftd2xx are provided. A #define selects which flavor is actually active. I could implement the same mechanism and add this switch to the configure script. The readability of ftdi.c would lose a bit with all the #ifdef / #else stuff but it'd be pretty straight forward. Are there any objections against supporting closed source libraries with UrJTAG? We'd still have the open source libftdi in place. Cheers Arnim |