Closed GoogleCodeExporter closed 9 years ago
The ftdi_usb_purge_tx_buffer and ftdi_usb_purge_buffers were added when
troubleshooting issues with the Transfer function, are certainly unnecessary,
and have been removed.
The ftdi_usb_purge_rx_buffer was originally necessary, although my initial
testing agrees with your assessment that SPI reads seem to work fine without it
and my code comments are woefully inadequate to determine if it can be safely
removed.
Until further testing can be done, by default ftdi_usb_purge_rx_buffer will be
called each time raw_read is called, but I've made this a configurable option.
You can disable the buffer purge by calling FlushAfterRead(0).
Original comment by heffne...@gmail.com
on 31 Jan 2013 at 3:50
After testing, both SPI and I2C function properly with flushing disabled; this
is now the default. It can be re-enabled if desired by calling
FlushAfterRead(1).
Original comment by heffne...@gmail.com
on 22 Mar 2013 at 4:28
Original issue reported on code.google.com by
epooc...@gmail.com
on 31 Jan 2013 at 5:43