Document the FT245R EEPROM weirdness

The FT232R and the FT245R share the same USB id (0x0403, 0x6001) and are
only distinguished by bit 00.0 in the (internal) EEPROM.

ftdi_eeprom currently can't handle this and will turn an FT245R chip
into an FT232R; document the fact.

Signed-off-by: Anders Larsen <al@alarsen.net>

diff --git a/doc/EEPROM-structure b/doc/EEPROM-structure
index a1e9b02..08abe62 100644 (file)
--- a/doc/EEPROM-structure
+++ b/doc/EEPROM-structure
@@ -9,7 +9,7 @@ Type   |  Use extra EEPROM space
 FT2XXB |  No
 
 Byte.BIT| TYPE_AM TYPE_BM   TYPE_2232C       TYPE_R          TYPE_2232H       TYPE_4232H
-00.0    |      0       0   channel_a_type                    channel_a_type   0
+00.0    |      0       0   channel_a_type   232R/245R        channel_a_type   0
 00.1    |      0       0   channel_a_type                    channel_a_type   0
 00.2    |      0       0   channel_a_type   high_current     channel_a_type   0
 00.3    |      0       0   channel_a_driver channel_a_driver channel_a_driver channel_a_driver
@@ -18,6 +18,7 @@ Byte.BIT| TYPE_AM TYPE_BM   TYPE_2232C       TYPE_R          TYPE_2232H       TY
 00.6    |      0       0   0                0                0                0
 00.7    |      0       0   0                0                SUSPEND_DBUS7    channel_c_driver
 
+On TYPE_R 00.0 is set for the FT245R and cleared for the FT232R
 On TYPE_R 00.3 set mean D2XX, on other devices VCP
 
 01.0    |      0       0   channel_b_type                    channel_b_type   0