libftdi  

Messages by Thread

• • Re: ftdi_set_bitmode question Joachim Schambach
  • Re: ftdi_set_bitmode question Uwe Bonnes
  • Re: ftdi_set_bitmode question Joachim Schambach
  • Re: ftdi_set_bitmode question Uwe Bonnes
  • Re: ftdi_set_bitmode question Joachim Schambach
• ftdi_eeprom and FT4232H Robert Pearce
  • Re: ftdi_eeprom and FT4232H Uwe Bonnes
  • Re: ftdi_eeprom and FT4232H Xiaofan Chen
  • Re: ftdi_eeprom and FT4232H Uwe Bonnes
  • Re: ftdi_eeprom and FT4232H Thomas Jarosch
• (1.0/ to apply after last 10/10)Next try to get the encoding/decoding for the different FT2232/FT232H chip modes right Uwe Bonnes
• (1.0/src/ftdi.c/10/10)Use default vendor/product strings for EEPROM when user doesn't supply some Uwe Bonnes
  • Re: (1.0/src/ftdi.c/10/10)Use default vendor/product strings for EEPROM when user doesn't supply some Thomas Jarosch
• (1.0/examples/serial_test.c/9/10)Rename to serial-test, as write can now also be choosen, search for any devices with one of the default VID/PID, if no VID/PID if given Uwe Bonnes
• (1.0//8/10)Rename serial_read to serial_test, as now write is also possible Uwe Bonnes
• (1.0/src/ftdi.c/7/10)Rewrite the baudrate calculation, tested for 232R and 232H Uwe Bonnes
  • Re: (1.0/src/ftdi.c/7/10)Rewrite the baudrate calculation, tested for 232R and 232H Thomas Jarosch
  • Re: (1.0/src/ftdi.c/7/10)Rewrite the baudrate calculation, tested for 232R and 232H Thomas Jarosch
• (1.0/examples/eeprom.c/6/10)Give usage hints for handling empty EEPROM Uwe Bonnes
• (1.0/src/ftdi.c/5/10):FT232H has even more config bytes and less user_area Uwe Bonnes
• (1.0/examples/eeprom.c/4/10)Only try ftdi_usb_open_dev if devices found Uwe Bonnes
• (1.0/src/ftdi.c/ 3/10)FT232H: Baud rate generation is the same as with FT2232H/FT232H Uwe Bonnes
• (1.0/ftdi_eeprom/main.c/2/10): Move opening the Device before tampering with the values, Move reading the device just after opening Uwe Bonnes
• Try to inihibit programming EEPROM with data for a different device and zero EEPROM memory image early Uwe Bonnes
• libftdi-1.0 MinGW Windows Development Kit snapshot Xiaofan Chen
  • Re: libftdi-1.0 MinGW Windows Development Kit snapshot Xiaofan Chen
• Re: from bb-mode back to uart Xiaofan Chen
  • Re: from bb-mode back to uart Xiaofan Chen
  • Re: from bb-mode back to uart Uwe Bonnes
  • Re: from bb-mode back to uart Xiaofan Chen
  • RE: from bb-mode back to uart Ale Max
  • RE: from bb-mode back to uart Uwe Bonnes
  • Re: from bb-mode back to uart Xiaofan Chen
• ftdi_eeprom: Change handling the EEPROM size Uwe Bonnes
• [no subject] Uwe Bonnes
• [no subject] Uwe Bonnes
• Add ftdi_set_eeprom_buf() as proposed in ftdi_eeprom Uwe Bonnes
• Add missing ftdi_get|set_eeprom_value entries Uwe Bonnes
• SPI communication with libftdi brunosmmm
  • Re: SPI communication with libftdi Xiaofan Chen
• 0.18: Add H-Type specific MPSSE definitions Uwe Bonnes
• 0.18: Fix ftdi.h directory when using cmake/make package Uwe Bonnes
  • Re: 0.18: Fix ftdi.h directory when using cmake/make package Thomas Jarosch
• [no subject] Uwe Bonnes
  • Re: Try to inihibit programming EEPROM with data for a different device Thomas Jarosch
  • Re: Try to inihibit programming EEPROM with data for a different device Uwe Bonnes
  • Re: Try to inihibit programming EEPROM with data for a different device Rodrigo Rosa
  • Re: Try to inihibit programming EEPROM with data for a different device Uwe Bonnes
  • Re: Try to inihibit programming EEPROM with data for a different device Uwe Bonnes
  • Re: Try to inihibit programming EEPROM with data for a different device Thomas Jarosch
  • Re: Try to inihibit programming EEPROM with data for a different device Uwe Bonnes
• [no subject] Uwe Bonnes
• [no subject] Uwe Bonnes
• [1.0] Try to inihibit programming EEPROM with data for a different device Uwe Bonnes
  • Re: [1.0] Try to inihibit programming EEPROM with data for a different device Thomas Jarosch
• overwrite the current EEPROM of a FT232RL Johannes D.
  • Re: overwrite the current EEPROM of a FT232RL Uwe Bonnes
  • Re: overwrite the current EEPROM of a FT232RL Uwe Bonnes
  • Re: overwrite the current EEPROM of a FT232RL Johannes D.
  • Re: overwrite the current EEPROM of a FT232RL Uwe Bonnes
  • Re: overwrite the current EEPROM of a FT232RL Johannes D.
• libftdi-0.19 32bit/64bit Windows binaries Xiaofan Chen
  • Re: libftdi-0.19 32bit/64bit Windows binaries Xiaofan Chen
  • Re: libftdi-0.19 32bit/64bit Windows binaries Uwe Bonnes
  • Re: libftdi-0.19 32bit/64bit Windows binaries Xiaofan Chen
• bitbang on FT232R / FT245R Giampaolo Bellini
  • RE: bitbang on FT232R / FT245R Spindler, Tyler L
• 1.0: Allow to search for all FTDI standard VID/PID Uwe Bonnes
  • Re: 1.0: Allow to search for all FTDI standard VID/PID Thomas Jarosch
  • Re: 1.0: Allow to search for all FTDI standard VID/PID Uwe Bonnes
  • Re: 1.0: Allow to search for all FTDI standard VID/PID Thomas Jarosch
  • Re: 1.0: Allow to search for all FTDI standard VID/PID Uwe Bonnes
  • Re: 1.0: Allow to search for all FTDI standard VID/PID Thomas Jarosch
  • Re: 1.0: Allow to search for all FTDI standard VID/PID Xiaofan Chen
  • Re: 1.0: Allow to search for all FTDI standard VID/PID Thomas Jarosch
• 1.0/examples/find_all: Don't return before cleanup Uwe Bonnes
• 1.0: Add the list retrieved by libusb_get_device_list to the ftdi_context and only release it on exit Uwe Bonnes
• Re: [libftdi 0.18] SPI with CBUS Bit-banging FT232H Xiaofan Chen
  • Re: [libftdi 0.18] SPI with CBUS Bit-banging FT232H Alex Stefan
  • Re: [libftdi 0.18] SPI with CBUS Bit-banging FT232H Uwe Bonnes
  • Re: [libftdi 0.18] SPI with CBUS Bit-banging FT232H Alex Stefan
  • Re: [libftdi 0.18] SPI with CBUS Bit-banging FT232H Uwe Bonnes
  • Re: [libftdi 0.18] SPI with CBUS Bit-banging FT232H Alex Stefan
  • Re: [libftdi 0.18] SPI with CBUS Bit-banging FT232H Uwe Bonnes
  • Re: [libftdi 0.18] SPI with CBUS Bit-banging FT232H Alex Stefan
  • Re: [libftdi 0.18] SPI with CBUS Bit-banging FT232H Uwe Bonnes
  • Re: [libftdi 0.18] SPI with CBUS Bit-banging FT232H Xiaofan Chen
• [1.0] 2 invalid frees and multiple invalid reads and writes in ftdi_usb_get_strings Matthias Janke
  • Re: [1.0] 2 invalid frees and multiple invalid reads and writes in ftdi_usb_get_strings Matthias Janke
  • Re: [1.0] 2 invalid frees and multiple invalid reads and writes in ftdi_usb_get_strings Matthias Janke
  • Re: [1.0] 2 invalid frees and multiple invalid reads and writes in ftdi_usb_get_strings Uwe Bonnes
  • Re: [1.0] 2 invalid frees and multiple invalid reads and writes in ftdi_usb_get_strings Matthias Janke
  • [1.0] Increment the refcount on devices we return from ftdi_usb_find_all(), was: Re: [1.0] 2 invalid frees Uwe Bonnes
  • Re: [1.0] Increment the refcount on devices we return from ftdi_usb_find_all(), was: Re: [1.0] 2 invalid frees Matthias Janke
• _ftdi_determine_max_packet_size reports wrong value in some cases Алексей Косилин
  • Re: _ftdi_determine_max_packet_size reports wrong value in some cases Xiaofan Chen
  • Re: _ftdi_determine_max_packet_size reports wrong value in some cases Алексей Косилин
  • Re: _ftdi_determine_max_packet_size reports wrong value in some cases Xiaofan Chen
  • Re: _ftdi_determine_max_packet_size reports wrong value in some cases Xiaofan Chen
  • Re: _ftdi_determine_max_packet_size reports wrong value in some cases Xiaofan Chen
  • Re: _ftdi_determine_max_packet_size reports wrong value in some cases Алексей Косилин
  • Re: _ftdi_determine_max_packet_size reports wrong value in some cases Xiaofan Chen
  • Re: _ftdi_determine_max_packet_size reports wrong value in some cases Алексей Косилин
  • Re: _ftdi_determine_max_packet_size reports wrong value in some cases Xiaofan Chen
• set 'serial' not working Xiangfu Liu
  • Re: set 'serial' not working Xiangfu Liu
• 1.0/src/ftdi_stream.c: Check for fitting device Uwe Bonnes
• 1.0/examples/stream_test: Fix memory leakage pathes Uwe Bonnes
• 1.0/examples: Fix all leak in the examples shown with no device connected Uwe Bonnes
• 1.0/src/ftdi.c: Free the device list in ftdi_usb_find_all Uwe Bonnes
• memory leak in examples/find_all.c (1.0) Matthias Janke
  • Re: memory leak in examples/find_all.c (1.0) Uwe Bonnes
  • Re: memory leak in examples/find_all.c (1.0) Xiaofan Chen
  • 1.0/src/ftdi.c: Don't leak ctx, was: Re: memory leak in examples/find_all.c (1.0) Uwe Bonnes
• 1.0/example/baud_test.c: Clean up on error Uwe Bonnes
• 1.0/examples/eeprom.c: Clean up in error pathes Uwe Bonnes
• Add missing check for NULL product string Uwe Bonnes
• 1.0/src/ftdi.c: Fix calculation of the Mode Bitfield Uwe Bonnes
• 1.0/examples/eeprom.c: Remove-other-duplicate-code Uwe Bonnes
• 1.0/examples/eeprom.c: Abort if no EEPROM is found Uwe Bonnes
• Remove some code duplication Uwe Bonnes
• libftdi-1.0 API documentation enhancement Xiaofan Chen
• Location of libftdi-1.0 header ftdi.h different from libftdi-0.19 Xiaofan Chen
  • Re: Location of libftdi-1.0 header ftdi.h different from libftdi-0.19 Uwe Bonnes
  • Re: Location of libftdi-1.0 header ftdi.h different from libftdi-0.19 Xiaofan Chen
  • Re: Location of libftdi-1.0 header ftdi.h different from libftdi-0.19 Xiaofan Chen
  • Re: Location of libftdi-1.0 header ftdi.h different from libftdi-0.19 Uwe Bonnes
  • Re: Location of libftdi-1.0 header ftdi.h different from libftdi-0.19 Xiaofan Chen
  • Re: Location of libftdi-1.0 header ftdi.h different from libftdi-0.19 Uwe Bonnes
  • Re: Location of libftdi-1.0 header ftdi.h different from libftdi-0.19 Xiaofan Chen
  • Re: Location of libftdi-1.0 header ftdi.h different from libftdi-0.19 Thomas Jarosch
  • Re: Location of libftdi-1.0 header ftdi.h different from libftdi-0.19 Xiaofan Chen
• libftdi-1.0: One more FT232H related patch Uwe Bonnes
• Backport FT232H support to 0.1x Uwe Bonnes
  • Re: Backport FT232H support to 0.1x Michael Markstaller
• libftdi-1.0 branch: Support FT232H Uwe Bonnes
  • Re: libftdi-1.0 branch: Support FT232H Thomas Jarosch
  • Re: libftdi-1.0 branch: Support FT232H Uwe Bonnes
  • Re: libftdi-1.0 branch: Support FT232H Thomas Jarosch
  • Re: libftdi-1.0 branch: Support FT232H Thomas Jarosch
• FT2232H asynchronous maximum data rates? Caleb Kemere
  • Re: FT2232H asynchronous maximum data rates? Uwe Bonnes
  • Re: FT2232H asynchronous maximum data rates? Caleb Kemere
  • Re: FT2232H asynchronous maximum data rates? Caleb Kemere
  • Re: FT2232H asynchronous maximum data rates? Uwe Bonnes
  • Re: FT2232H asynchronous maximum data rates? Caleb Kemere
  • Re: FT2232H asynchronous maximum data rates? Xiaofan Chen
  • Re: FT2232H asynchronous maximum data rates? Caleb Kemere
  • Re: FT2232H asynchronous maximum data rates? Xiaofan Chen
  • Re: FT2232H asynchronous maximum data rates? Caleb Kemere
  • Re: FT2232H asynchronous maximum data rates? Xiaofan Chen
  • Re: FT2232H asynchronous maximum data rates? Caleb Kemere
  • Re: FT2232H asynchronous maximum data rates? Xiaofan Chen
  • Re: FT2232H asynchronous maximum data rates? Xiaofan Chen
• proper use of ftdi_read_data() Caleb Kemere
• Disconnect by usbfs, /dev/ttyUSB0 disappears when using libftdi Michael Soire
  • RE: Disconnect by usbfs, /dev/ttyUSB0 disappears when using libftdi Michael Plante
  • Re: Disconnect by usbfs, /dev/ttyUSB0 disappears when using libftdi Thomas Jarosch
• [ANNOUNCE] libftdi 0.19 released Thomas Jarosch
• libusb_init and libusb_exit in libftdi-1.0 David Wiberg
  • Re: libusb_init and libusb_exit in libftdi-1.0 Thomas Jarosch
  • Re: libusb_init and libusb_exit in libftdi-1.0 David Wiberg
  • Re: libusb_init and libusb_exit in libftdi-1.0 Xiaofan Chen
  • Re: libusb_init and libusb_exit in libftdi-1.0 Uwe Bonnes
  • Re: libusb_init and libusb_exit in libftdi-1.0 Thomas Jarosch
• What blocks master and eeprom/new from a merge? Uwe Bonnes
  • Re: What blocks master and eeprom/new from a merge? Thomas Jarosch
  • libftdi1: Fixe Fixme in CBUS decoding Uwe Bonnes
  • Re: libftdi1: Fixe Fixme in CBUS decoding Thomas Jarosch
  • Re: libftdi1: Fixe Fixme in CBUS decoding Uwe Bonnes
  • Re: libftdi1: Fixe Fixme in CBUS decoding Thomas Jarosch
• getbitmode() and cbus pins. Mark Rages
  • Re: getbitmode() and cbus pins. Mark Rages
  • Re: getbitmode() and cbus pins. Thomas Jarosch
• libftdi 0.x: Release 0.19? Thomas Jarosch
  • Re: libftdi 0.x: Release 0.19? Mark Rages
  • Re: libftdi 0.x: Release 0.19? Thomas Jarosch
  • Re: libftdi 0.x: Release 0.19? Thomas Klose
  • Re: libftdi 0.x: Release 0.19? Thomas Jarosch
  • [PATCH] make module-unloading behavior flexible Thomas Klose
  • Re: [PATCH] make module-unloading behavior flexible Thomas Jarosch
  • Re: [PATCH] make module-unloading behavior flexible Thomas Klose
  • Re: libftdi 0.x: Release 0.19? Thomas Jarosch
• reading CBUS pins on FT232R? Mark Rages
• lbftdi for OpenWRT Michael Markstaller
  • Re: lbftdi for OpenWRT Michael Markstaller
  • Re: lbftdi for OpenWRT Uwe Bonnes
  • Re: lbftdi for OpenWRT Michael Markstaller
  • RE: lbftdi for OpenWRT Spindler, Tyler L
  • RE: lbftdi for OpenWRT Michael Markstaller
• Control bit-shift LED-Driver with FT4232H Michael Markstaller
  • Re: Control bit-shift LED-Driver with FT4232H Berni Joss
  • Re: Control bit-shift LED-Driver with FT4232H Michael Markstaller
• ftdi_poll_modem_status() results in upper byte of status being to to 0xFF Tom Saunders
  • Re: ftdi_poll_modem_status() results in upper byte of status being to to 0xFF Uwe Bonnes
  • Re: ftdi_poll_modem_status() results in upper byte of status being to to 0xFF Thomas Jarosch
• Some libftdi patches Evgeny Sinelnikov
  • Re: Some libftdi patches Thomas Jarosch
• RE: How to get receive or fetch data from external USB device (FDTI FT232BM chip) to android tab device ? Michael Plante
  • Re: How to get receive or fetch data from external USB device (FDTI FT232BM chip) to android tab device ? Tim Schneider

• Earlier messages
• Later messages