Hi Uwe, On 07/11/2011 03:12 PM, Uwe Bonnes wrote: > Thomas> IMHO it still breaks the ftdi_eeprom tool, doesn't it? > > Argh, > > I didn't realize that ftdi_eeprom is now a part of libftdi-1. > Please test appended patch together with the one you find offending as above. > > When ftdi_open happened before we tamper with the eeprom values, we have a > valid stub in the eeprom structure, no need set the chip type etc. > > Perhaps this fixes your case.
I've applied all your other patches. I'll apply the last one once I have access to my FTDI hardware at work. > B.T.w. ftdi_eeprom deosn't allow to reprogram VID/PID yet. The conf file > must supply VID/PID of the device to open and VIP/PID that should get > programmed into the device. Hmm, strange. Can't remember how we did it back in the days. We currently switched to use MProg as ftdi_eeprom didn't support the newer chip types back then. What we really should think about is to merge your eeprom tool and ftdi_eeprom. No need for two "official" tools :) Cheers, Thomas -- libftdi - see http://www.intra2net.com/en/developer/libftdi for details. To unsubscribe send a mail to [email protected]
