On Mon, Jul 25, 2011 at 5:04 PM, Uwe Bonnes <[email protected]> wrote: >>>>>> "Robert" == Robert Pearce <[email protected]> writes: > > Robert> Hello all, I'm new here. I have designed a system with an > Robert> FT4232H for which we are using a PID allocated by FTDI. I wanted > Robert> to use ftdi_eeprom to configure this (and avoid the painful > Robert> install-the-driver-eight-times-per-unit behaviour of Windoze) > Robert> but found it wouldn't do the job. The configuration file gave > Robert> the new PID and the program therefore couldn't see the blank > Robert> FT4232. > > Robert> I attach a patch (against current git, I hope) that fixes this, > Robert> by changing the fall-back behaviour to try the three defaults > Robert> for the various devices, rather than only the original one. > > For a recent libftdi-1, > i = ftdi_usb_open(&ftdi, 0, 0); > should do the same job then searching for all VIFDS/PID explicit. >
it seems to me that ftdi_eeprom has not been updated for a while and then it is absorbed in to libftdi-1.0 for the 1.0 branch and it seems to have better features than the ftdi_eeprom branch. http://developer.intra2net.com/git/?p=ftdi_eeprom Does this mean that ftdi_eeprom will not be further updated? In that case, then probably it is good to release libftdi-1.0 asap. -- Xiaofan -- libftdi - see http://www.intra2net.com/en/developer/libftdi for details. To unsubscribe send a mail to [email protected]
