[Discuss] ftdi chipset and linux

[Nuno Sucena Almeida]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/17/2013 07:52 AM, Scott Ehrlich wrote:
> From a chipset compatibility standpoint, what do people know about
> ftdi and linux?   I know I could always visit the ftdi page, but
> anyone with practical knowledge here would be great.

I've seen ftdi devices being uses for make different projects and never
heard of drivers issues:

http://www.ftdichip.com/Drivers/VCP.htm
"All FTDI devices now supported in Ubuntu 11.10, kernel 3.0.0-19
Refer to TN-101 if you need a custom VCP VID/PID in Linux"

http://www.ftdichip.com/Drivers/D2XX.htm
http://www.ftdichip.com/Drivers/D2XX/Linux/ReadMe-linux.txt
"
FTDI do not release the source code for libftd2xx.  If you prefer to
work with source code and are starting a project from scratch, consider
using the open-source libFTDI.
"

http://www.intra2net.com/en/developer/libftdi/
"
libFTDI is an open source library to talk to FTDI chips: FT232BM,
FT245BM, FT2232C, FT2232D, FT245R and FT232H including the popular
bitbang mode. The library is linked with your program in userspace, no
kernel driver required.

libFTDI works perfectly with Linux, Windows, MacOS X and BSD variants
thanks to libusb.
"

regards,
Nuno

- -- 
http://aeminium.org/nuno/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBAgAGBQJQ+AteAAoJEPIY6fuKMkz5tSYP/iaBiYS9HP2QcUt15ztkupe0
Bx5Q/hUCsdaj7OEElW9rXAcRQg4pUxuvI6eqQ/DWgvctexJTyNm8LJZ7AmFe1ir4
MhfILdwmdZUpLxzLDuryONy5C6F/ZTVaJ0gOx09LKHLK7jmKozNCVacaV+cHfVBx
9vCbp/+TegAsLuv264h1jYuXQQ01c6BlgjO1M+mLXMTsOBMZLJMhliBlX7CnH3Qa
fgp0qQOMsCqezIXchk3iDQSmaFfbYG37qSo0ZysRxZCU/U9O0XLZpCK28pqnpsLo
poGAcc2yOkgfKYJJpaFjo84owAcE6YpBkJNEhPD0KAkA9Ckj1Iy2p03tZmdRQ92u
xvI5OEnyfBk+2Eab/pE4eJcO5dCiMgdAVopHlW1iLng6+rvwwd2VNWARx7CJbdK9
zPa3JLCCjcHgrbOHbu0CVOWMxq5QzEVviA6S3ZXDQFQZsG/j21krJetis8TB/O7A
9oCF99ls8Cxxlr6GnqEx3NSk3Zkv02ngx2XHd71TU36VYh6Z2AsYHSepQb2cgF8h
MvDRfUGpdCSvXUnu4cn93+v6WqRWD21IOQiuqm3ZNxTs72no6VA0FThl1SeVMWic
GqDvxwdjgW5cye5bwka9leqpgA57AOml4o7iNXnwQgxoXwzfEmXmjq7g+qlp8pfH
mUU1V6kqzbBGyV+IRdFE
=GY3m
-----END PGP SIGNATURE-----