libftdi  

Messages by Thread

• • Re: How do you use libftdi with the FT245R? Aaron Jacobs
  • Re: How do you use libftdi with the FT245R? Uwe Bonnes
  • Re: How do you use libftdi with the FT245R? Aaron Jacobs
• How to do this with libftdi ? Rui Barreiros
• RE: FT4232H, TI ADS7871 A/D Converter Michael Plante
  • Re: FT4232H, TI ADS7871 A/D Converter Xiaofan Chen
• FW: FTDI 4232H and TI ADS7871 A/D Converter Michael Plante
• Patch queue Thomas Jarosch
• release? Bert Vermeulen
  • Re: release? Uwe Bonnes
  • Re: release? Xiaofan Chen
  • Re: release? Thomas Jarosch
• Should ftdi_read_data_submit_to() be a new call? Uwe Bonnes
  • Re: Should ftdi_read_data_submit_to() be a new call? Xiaofan Chen
  • Re: Should ftdi_read_data_submit_to() be a new call? Thomas Jarosch
  • RE: Should ftdi_read_data_submit_to() be a new call? Michael Plante
  • Re: Should ftdi_read_data_submit_to() be a new call? Thomas Jarosch
  • RE: Should ftdi_read_data_submit_to() be a new call? Michael Plante
  • Re: Should ftdi_read_data_submit_to() be a new call? Thomas Jarosch
  • Re: Should ftdi_read_data_submit_to() be a new call? Uwe Bonnes
  • RE: Should ftdi_read_data_submit_to() be a new call? Michael Plante
  • Re: Should ftdi_read_data_submit_to() be a new call? Uwe Bonnes
  • Re: Should ftdi_read_data_submit_to() be a new call? Thomas Jarosch
• libftdi-1: Add version of ftdi_read_data_submit with timeout Uwe Bonnes
• Better explanation of ftdi_read_data() behaviour Uwe Bonnes
• Building the git repository sources to a different prefix directory Drasko DRASKOVIC
  • Re: Building the git repository sources to a different prefix directory Uwe Bonnes
  • Re: Building the git repository sources to a different prefix directory Drasko DRASKOVIC
  • Re: Building the git repository sources to a different prefix directory Drasko DRASKOVIC
  • Re: Building the git repository sources to a different prefix directory Uwe Bonnes
  • Re: Building the git repository sources to a different prefix directory Drasko DRASKOVIC
  • Re: Building the git repository sources to a different prefix directory Xiaofan Chen
• ft2232_read() error: couldn't read enough bytes from FT2232 device (0 < 5) Drasko DRASKOVIC
  • Re: ft2232_read() error: couldn't read enough bytes from FT2232 device (0 < 5) Uwe Bonnes
  • Re: ft2232_read() error: couldn't read enough bytes from FT2232 device (0 < 5) Drasko DRASKOVIC
  • Re: ft2232_read() error: couldn't read enough bytes from FT2232 device (0 < 5) Xiaofan Chen
  • Re: ft2232_read() error: couldn't read enough bytes from FT2232 device (0 < 5) Drasko DRASKOVIC
• Detecting deprecated function Markus Dolze
• Re: libftdi@developer.intra2net.com is a subscribers only list Petr Jakeš
  • Re: libftdi@developer.intra2net.com is a subscribers only list Emmanuel Blot
  • RE: libftdi@developer.intra2net.com is a subscribers only list Michael Plante
  • Re: libftdi@developer.intra2net.com is a subscribers only list Vladimir Yakovlev
  • Re: libftdi@developer.intra2net.com is a subscribers only list Petr Jakeš
  • RE: libftdi@developer.intra2net.com is a subscribers only list Michael Plante
  • Re: libftdi@developer.intra2net.com is a subscribers only list Vladimir Yakovlev
  • Re: libftdi@developer.intra2net.com is a subscribers only list Petr Jakeš
  • Re: libftdi@developer.intra2net.com is a subscribers only list Emmanuel Blot
  • Re: libftdi@developer.intra2net.com is a subscribers only list Petr Jakeš
  • RE: libftdi@developer.intra2net.com is a subscribers only list Michael Plante
  • Re: libftdi@developer.intra2net.com is a subscribers only list Petr Jakeš
  • how to set receieve event in libftdi-0.18 Wu, Ruiyu (GE Healthcare)
  • RE: how to set receieve event in libftdi-0.18 Michael Plante
  • RE: how to set receieve event in libftdi-0.18 Wu, Ruiyu (GE Healthcare)
  • Re: how to set receieve event in libftdi-0.18 Xiaofan Chen
  • Re: how to set receieve event in libftdi-0.18 Xiaofan Chen
  • RE: how to set receieve event in libftdi-0.18 Michael Plante
  • how to realize read timeout in libftdi-0.18 Wu, Ruiyu (GE Healthcare)
  • RE: how to realize read timeout in libftdi-0.18 Michael Plante
  • Re: how to realize read timeout in libftdi-0.18 Xiaofan Chen
• Re: sending a break signal DJ Delorie
  • RE: sending a break signal Reha Elci
• FW: how to compile the libftdi-0.18 in ARM　platform :/usr/lib/libusb.so: could not read symbols: File in wrong format Wu, Ruiyu (GE Healthcare)
  • Re: FW: how to compile the libftdi-0.18 in ARM　platform :/usr/lib/libusb.so: could not read symbols: File in wrong format Teemu Peltola
  • RE: FW: how to compile the libftdi-0.18 in ARM　platform :/usr/lib/libusb.so: could not read symbols: File in wrong format Wu, Ruiyu (GE Healthcare)
  • Re: FW: how to compile the libftdi-0.18 in ARM　platform :/usr/lib/libusb.so: could not read symbols: File in wrong format Teemu Peltola
  • RE: FW: how to compile the libftdi-0.18 in ARM　platform :/usr/lib/libusb.so: could not read symbols: File in wrong format Wu, Ruiyu (GE Healthcare)
  • Re: FW: how to compile the libftdi-0.18 in ARM　platform :/usr/lib/libusb.so: could not read symbols: File in wrong format Teemu Peltola
• libftdi - Python SWIG & unsigned char * Chris Zeh
  • Re: libftdi - Python SWIG & unsigned char * Thomas Jarosch
  • Re: libftdi - Python SWIG & unsigned char * Chris Zeh
  • Re: libftdi - Python SWIG & unsigned char * Thomas Jarosch
• FT2232H sync fifo mode Thomas Heller
  • Re: FT2232H sync fifo mode Uwe Bonnes
  • Re: FT2232H sync fifo mode Thomas Heller
• only two of four SPI modes supported by FT4232H?? stefan harjes
  • RE: AW: only two of four SPI modes supported by FT4232H?? stefan harjes
  • Re: AW: only two of four SPI modes supported by FT4232H?? Berni Joss
  • Re: only two of four SPI modes supported by FT4232H?? Elberlee
  • AW: only two of four SPI modes supported by FT4232H?? stefan harjes
  • Re: only two of four SPI modes supported by FT4232H?? Stany MARCEL
  • Re: only two of four SPI modes supported by FT4232H?? Elberlee
  • Re: only two of four SPI modes supported by FT4232H?? Elberlee
  • Re: only two of four SPI modes supported by FT4232H?? Stany MARCEL
• ftdi_read_data return 0xff Rodrigo Rosa
  • RE: ftdi_read_data return 0xff Michael Plante
  • RE: ftdi_read_data return 0xff Michael Plante
  • Re: ftdi_read_data return 0xff Rodrigo Rosa
  • RE: ftdi_read_data return 0xff Michael Plante
  • Re: ftdi_read_data return 0xff Rodrigo Rosa
  • RE: ftdi_read_data return 0xff Michael Plante
  • Re: ftdi_read_data return 0xff Rodrigo Rosa
  • RE: ftdi_read_data return 0xff Michael Plante
  • Re: ftdi_read_data return 0xff Rodrigo Rosa
  • RE: ftdi_read_data return 0xff Michael Plante
  • Re: ftdi_read_data return 0xff Rodrigo Rosa
  • RE: ftdi_read_data return 0xff Michael Plante
• Error handling in streamtest Uwe Bonnes
  • Re: Error handling in streamtest Thomas Jarosch
  • Re: Error handling in streamtest Uwe Bonnes
  • Re: Error handling in streamtest Thomas Jarosch
• Call ftdi_usb_close_internal and not libusb_close Uwe Bonnes
• Check pointeer_before_ access Uwe Bonnes
• Make streamtest work on allocated structure Uwe Bonnes
• [PATCH] fixed open-function of cpp-wrapper Peter Schneider
  • Re: [PATCH] fixed open-function of cpp-wrapper Peter Schneider
  • Re: [PATCH] fixed open-function of cpp-wrapper Thomas Jarosch
  • Re: [PATCH] fixed open-function of cpp-wrapper Thomas Jarosch
• Crash on unplug Tim Schneider
  • Re: Crash on unplug Uwe Bonnes
  • Re: Crash on unplug Tim Schneider
  • RE: Crash on unplug Michael Plante
  • Re: Crash on unplug Thomas Jarosch
  • Re: Crash on unplug Uwe Bonnes
  • Re: Crash on unplug Uwe Bonnes
  • Re: Crash on unplug Xiaofan Chen
• libftdi i2c code sample bruno pennec
• Safer initialisation of ftdi_readstream Uwe Bonnes
  • Re: Safer initialisation of ftdi_readstream Thomas Jarosch
• Delete some remaining debug printout Uwe Bonnes
• Bug in libftdipp Context::open() pitpompej
  • Re: Bug in libftdipp Context::open() Thomas Jarosch
  • Re: Bug in libftdipp Context::open() Thomas Jarosch
  • Re: Re: Bug in libftdipp Context::open() Peter Schneider
• FT4232H Mini Module bitbang problem Teemu Peltola
  • Re: FT4232H Mini Module bitbang problem Teemu Peltola
• [PATCH 1/2] New configuration option default_pid Vladimir Yakovlev
  • [PATCH 2/2] Not writing to file, in flash_raw mode Vladimir Yakovlev
  • Re: [PATCH 2/2] Not writing to file, in flash_raw mode Thomas Jarosch
• libftdi vs. ftdi_sio Paul Fox
  • Re: libftdi vs. ftdi_sio Uwe Bonnes
  • Re: libftdi vs. ftdi_sio Paul Fox
  • Re: libftdi vs. ftdi_sio Jim Paris
  • Re: libftdi vs. ftdi_sio Paul Fox
  • Re: libftdi vs. ftdi_sio Jim Paris
• ftdi_usb_open_dev & ftdi_set_baudrate Tim Schneider
  • Re: ftdi_usb_open_dev & ftdi_set_baudrate Thomas Jarosch
  • Re: ftdi_usb_open_dev & ftdi_set_baudrate Tim Schneider
  • Re: ftdi_usb_open_dev & ftdi_set_baudrate Uwe Bonnes
  • Re: ftdi_usb_open_dev & ftdi_set_baudrate Tim Schneider
• ftdi_eeprom: Initial eeprom size Thomas Jarosch
  • Re: ftdi_eeprom: Initial eeprom size Uwe Bonnes
• Fix mantainer in CMakeLists.txt Uwe Bonnes
  • Re: Fix mantainer in CMakeLists.txt Thomas Jarosch
• Baudrate for bitbang mode Patrick Domack
• [PATCH] Proper initialisation of interface A. Vladimir Yakovlev
  • ftdi_eeprom 1.0 Morgane Vallée (aeris)
  • Re: ftdi_eeprom 1.0 Thomas Jarosch
  • Re: ftdi_eeprom 1.0 Morgane Vallée (aeris)
  • Re: ftdi_eeprom 1.0 Xiaofan Chen
  • Re: ftdi_eeprom 1.0 Thomas Jarosch
  • Re: ftdi_eeprom 1.0 Morgane Vallée (aeris)
  • Re: [PATCH] Proper initialisation of interface A. Thomas Jarosch
  • Re: [PATCH] Proper initialisation of interface A. Vladimir Yakovlev
  • Re: [PATCH] Proper initialisation of interface A. Thomas Jarosch
  • Re: [PATCH] Proper initialisation of interface A. Vladimir Yakovlev
  • Re: [PATCH] Proper initialisation of interface A. Thomas Jarosch
  • Re: [PATCH] Proper initialisation of interface A. Vladimir Yakovlev
• Trouble with libftdi on ARM Tyler Cordrey
  • RE: Trouble with libftdi on ARM Spindler, Tyler L
• Patch for ftdi_eeprom_decode() Tamas Vincze
  • Re: Patch for ftdi_eeprom_decode() Uwe Bonnes
  • Re: Patch for ftdi_eeprom_decode() Thomas Jarosch
• Re: [flashrom] [PATCH 3/5] ft2232_spi: allow CLOCK_X5 to be set at runtime Carl-Daniel Hailfinger
  • Re: [flashrom] [PATCH 3/5] ft2232_spi: allow CLOCK_X5 to be set at runtime Carl-Daniel Hailfinger
  • Re: [flashrom] [PATCH 3/5] ft2232_spi: allow CLOCK_X5 to be set at runtime Thomas Jarosch
• CFRunLoopLock error on Mac OS X Dan Loader
  • Re: CFRunLoopLock error on Mac OS X Dan Loader
  • Re: CFRunLoopLock error on Mac OS X Thomas Jarosch
• usb bulk write fails Newell Jensen
  • Re: usb bulk write fails Thomas Jarosch
  • Re: usb bulk write fails Newell Jensen
• FT232R DMX512 Rui Barreiros
  • Re: FT232R DMX512 Thomas Jarosch
  • Re: FT232R DMX512 Rui Barreiros
• libftdispi Stany MARCEL
  • Re: libftdispi Thomas Jarosch
• ftdi_usb_close() error Mikael Krus
  • RE: ftdi_usb_close() error Michael Plante
  • Re: ftdi_usb_close() error Mikael Krus
  • RE: ftdi_usb_close() error Michael Plante
  • Re: ftdi_usb_close() error Xiaofan Chen
  • Using both interfaces on FT2232H Mikael Krus
  • Re: Using both interfaces on FT2232H Will Zhang
  • Re: Using both interfaces on FT2232H Mikael Krus
  • Re: Using both interfaces on FT2232H Will Zhang
  • Re: Using both interfaces on FT2232H Mikael Krus
  • Re: Using both interfaces on FT2232H Mikael Krus
  • Re: ftdi_usb_close() error Uwe Bonnes
• FYI: libusb-win32 1.2.2.0 released Xiaofan Chen
  • Re: FYI: libusb-win32 1.2.2.0 released Uwe Bonnes
  • Re: FYI: libusb-win32 1.2.2.0 released Xiaofan Chen
• Design decisions, was: Re: Claiming devices... Uwe Bonnes
  • Re: Design decisions, was: Re: Claiming devices... Xiaofan Chen
  • RE: Design decisions, was: Re: Claiming devices... Michael Plante
• Claiming devices has no effect under Linux Thomas Klose
  • Re: Claiming devices has no effect under Linux Thomas Jarosch
  • Re: Claiming devices has no effect under Linux Thomas Klose
  • Re: Claiming devices has no effect under Linux Thomas Jarosch
  • Re: Claiming devices has no effect under Linux Thomas Klose
  • Re: Claiming devices has no effect under Linux Thomas Klose

• Earlier messages
• Later messages