>>>>> "Thomas" == Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx> writes:
Thomas> Hello Uwe, I started converting ftdi_eeprom to the new eeprom
Thomas> API and got quite far.
Thomas> What's a bit messy is how we currently handle the
Thomas> ftdi->eeprom->size field:
Thomas> It gets initialized with -1 and in ftdi_read_eeprom() we try to
Thomas> guess the real size later on.
Thomas> Which eeprom size should we assume in ftdi_eeprom tool?
Thomas> MAX_EEPROM_SIZE?
We can't assume any size. There may be no EEPROM soldered at all or a
46/56/66 and even an larger EEPROM may work. The FTDI chip handles 46/56/66
all different. So we can assume a size only after active writing to the
chip and we should delay deciding for a chip size only after probing.
Thomas> I'm finished for now, please have a look at the TODO entries in
Thomas> the "eeprom-new" branch. Once we have sorted out the initial
Thomas> eeprom size, Morgane can start working on the code.
Thomas> @Morgane: Or is that exactly the part you want to work on?
Thomas> Either way, feel free to send patches, I won't be able to work
Thomas> on this during the week.
I'll try to have a look next week.
--
Uwe Bonnes bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
