My current usage of libftdi is solely through the python bindings talking to a FT4232-based board. In that capacity, I spend much time at an ipython console
The attached patches first enable XML generation in doxygen, then generate docstrings for the python bindings from the function documentation in ftdi.c. It uses a BSD-licensed script to generate an .i file for SWIG which is then included from ftdi1.i. Having the docstrings available from a python console has been a nice addition over even the function signature only. On top of the bindings, I've made a custom SPI class which handles arbitrary port output bit(s) as chip-selects and a bit-banged I2C class that uses configurable pins for SDA/SCL and leaves the rest of the port bits as gpio's. If it gets extracted from the application-specific stuff, I'll post those somewhere public and ping the list. Thanks, Dan -- SDG www.whiteaudio.com -- libftdi - see http://www.intra2net.com/en/developer/libftdi for details. To unsubscribe send a mail to [email protected]
0001-Enable-doxygen-XML-output.patch
Description: Binary data
0002-Extract-doxygen-from-ftdi.c-to-python-docstrings.patch
Description: Binary data
