> It is said that libftdi 0.1x has compatibility problem with > libusb-compat. > http://libusb.6.n5.nabble.com/Status-of-async-mode-td7366.html#a7366 > http://www.mail-archive.com/[email protected]/msg00199.html
I see, thanks for the hint. Performed some more trials under the constraints that a) libusb 1 is installed $ pkg-config --modversion libusb-1.0 1.0.8 b) compat-layer for libusb 0.1 can't be removed $ pkg-config --modversion libusb 0.1.12 libftdi-1.0 from git -------------------- ./configure configure: error: this libftdi cannot be used with libusb-0.1, libusb-1.0 is needed ./configure --with-libusb=1.0 Detected libusb : 1.0 Detected libftdi : yes (have async mode) -> ft2232 driver works ./configure --with-libusb=1.0 --with-async-mode Detected libusb : 1.0 Detected libftdi : yes (have async mode) -> ft2232 driver works ./configure --with-libusb=0.1 -> same as without --with-libusb libftdi-0.18 ------------ ./configure Detected libusb : 0.1 Detected libftdi : yes (no async mode) -> ft2232 driver unstable, hangs in detect ./configure --with-libusb=1.0 configure: error: this libftdi cannot be used with libusb-1.0, libusb-0.1 is needed. did you configure libftdi with --with-async-mode ? The conclusion is quite simple: If libusb1 is installed, libftdi-1.0 is mandatory for UrJTAG to operate properly. Arnim ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ UrJTAG-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/urjtag-development
