# HG changeset patch
# User Mychaela Falconia <falcon@freecalypso.org>
# Date 1694409234 0
# Node ID f9ca05460238d11136dbef569d5c5d6bedd53b95
# Parent  17ffa6c66951b99719e8bb1ccddf1deed7263f04
rm eeproms/dumps: moved to fc-usbser-tools/artifacts

diff -r 17ffa6c66951 -r f9ca05460238 eeproms/dumps/FT232BM-RS232-cable
--- a/eeproms/dumps/FT232BM-RS232-cable	Mon Sep 11 04:17:09 2023 +0000
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,12 +0,0 @@
-# The following EEPROM image has been read out of a USB to RS232 (DE9M) cable
-# that contains an FT232BM chip; it is not clear if the cable itself is an FTDI
-# product or not.
-
-00: 0000 0403 6001 0400 16A0 0008 0110 0A94
-10: 2A9E 12C8 030A 0046 0054 0044 0049 032A
-20: 0055 0053 0042 0020 0053 0065 0072 0069
-30: 0061 006C 0020 0043 006F 006E 0076 0065
-40: 0072 0074 0065 0072 0312 0046 0054 0044
-50: 0049 0043 0033 0049 004B 0302 0000 0000
-60: 0000 0000 0000 0000 0000 0000 0000 0000
-70: 0000 0000 0000 0000 0000 0000 0001 C08B
diff -r 17ffa6c66951 -r f9ca05460238 eeproms/dumps/FT232R-specimen1
--- a/eeproms/dumps/FT232R-specimen1	Mon Sep 11 04:17:09 2023 +0000
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,13 +0,0 @@
-# This specimen has been read out from a no-name ebay-sourced FT232RL breakout
-# board; the FT232RL chip is suspect because the serial number string is
-# programmed to "00000000", whereas FTDI supposedly program true per-unit
-# serial numbers.
-
-00: 4000 0403 6001 0000 2DA0 0008 0000 0A98
-10: 20A2 12C2 1023 0005 030A 0046 0054 0044
-20: 0049 0320 0046 0054 0032 0033 0032 0052
-30: 0020 0055 0053 0042 0020 0055 0041 0052
-40: 0054 0312 0030 0030 0030 0030 0030 0030
-50: 0030 0030 0000 0001 0000 0000 0000 0000
-60: 0000 0000 0000 0000 0000 0000 0000 0000
-70: 0000 0000 0000 0000 0000 0000 0000 38AE
diff -r 17ffa6c66951 -r f9ca05460238 eeproms/dumps/FT232R-specimen2
--- a/eeproms/dumps/FT232R-specimen2	Mon Sep 11 04:17:09 2023 +0000
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,12 +0,0 @@
-# This specimen has been read out from George UberWaves' "FTDI Professional"
-# USB-serial cable with OsmocomBB branding; it is believed to be a genuine
-# FT232RL chip.
-
-00: 4000 0403 6001 0000 2DA0 0008 0000 0A98
-10: 20A2 12C2 1023 0005 030A 0046 0054 0044
-20: 0049 0320 0046 0054 0032 0033 0032 0052
-30: 0020 0055 0053 0042 0020 0055 0041 0052
-40: 0054 0312 0041 0039 0030 0033 0031 0048
-50: 0047 0036 B74D 90B9 0000 0000 0000 0000
-60: 0000 0000 0000 0000 0000 0000 0000 0000
-70: 0000 0000 0000 0000 0000 0000 0000 269F
diff -r 17ffa6c66951 -r f9ca05460238 eeproms/dumps/FT232R-specimen3
--- a/eeproms/dumps/FT232R-specimen3	Mon Sep 11 04:17:09 2023 +0000
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,11 +0,0 @@
-# This specimen has been read out from a UB232R module from Digi-Key;
-# it is believed to be a genuine FT232RQ chip.
-
-00: 4004 0403 6001 0600 2D80 0008 0200 0A98
-10: 0EA2 12B0 0043 0000 030A 0046 0054 0044
-20: 0049 030E 0055 0042 0032 0033 0032 0052
-30: 0312 0046 0054 0039 004C 0048 0053 004C
-40: 0043 0302 0001 0000 0000 0000 0000 0000
-50: 0000 0000 0000 0000 0000 0000 0000 0000
-60: 0000 0000 0000 0000 0000 0000 0000 0000
-70: 0000 0000 0000 0000 0000 0000 0000 95A0
diff -r 17ffa6c66951 -r f9ca05460238 eeproms/dumps/flyswatter1
--- a/eeproms/dumps/flyswatter1	Mon Sep 11 04:17:09 2023 +0000
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,30 +0,0 @@
-# The original Flyswatter (aka Flyswatter1) by TinCanTools is an
-# FT2232D-based buffered JTAG + UART adapter.  It has a 93C56 EEPROM
-# in which a custom set of textual ID strings have been programmed,
-# but the USB ID is still 0403:6010 (FT2232x default and signifying
-# a dual UART), causing the bogosity whereby the Linux kernel creates
-# two ttyUSB devices for both FT2232D channels, for the first out of
-# that pair to subsequently disappear when OpenOCD runs and starts
-# accessing Channel A for MPSSE JTAG via libusb.
-#
-# What follows is a dump of the EEPROM made from the FS1 board I managed
-# to score on ebay; given that the serial number string is set to "FS000000",
-# I am going to assume that the factory programming was the same on all
-# units, without unique serial numbers.
-
-00: 0000 0403 6010 0500 6480 0008 0200 1896
-10: 16AE 12C4 0056 0000 0000 0000 0000 0000
-20: 0000 0000 0000 0000 0000 0000 0000 0000
-30: 0000 0000 0000 0000 0000 0000 0000 0000
-40: 0000 0000 0000 0000 0000 0000 0000 0000
-50: 0000 0000 0000 0000 0000 0000 0000 0000
-60: 0000 0000 0000 0000 0000 0000 0000 0000
-70: 0000 0000 0000 0000 0000 0000 0000 0000
-80: 0000 0000 0000 0000 0000 0000 0000 0000
-90: 0000 0000 0000 0318 0054 0069 006E 0043
-A0: 0061 006E 0054 006F 006F 006C 0073 0316
-B0: 0046 006C 0079 0073 0077 0061 0074 0074
-C0: 0065 0072 0312 0046 0053 0030 0030 0030
-D0: 0030 0030 0030 0302 0000 0000 0000 0000
-E0: 0000 0000 0000 0000 0000 0000 0000 0000
-F0: 0000 0000 0000 0000 0000 0000 0000 8317
diff -r 17ffa6c66951 -r f9ca05460238 eeproms/dumps/om-debug-board-v3
--- a/eeproms/dumps/om-debug-board-v3	Mon Sep 11 04:17:09 2023 +0000
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,31 +0,0 @@
-# Openmoko's custom debug board for their Neo1973 and Neo FreeRunner
-# smartphones is an important piece of history; to the best of my
-# (Mychaela's) understanding, it was one of the first FT2232x devices
-# to formalize the idea of having the kernel create only one ttyUSB
-# device for Channel B (which is a standard UART), leaving Channel A
-# untouched for userspace applications like OpenOCD.  The feat is
-# accomplished by giving the device a custom USB ID (the one used by
-# OM for this debug board is 1457:5118), and teaching the ftdi_sio
-# driver in the Linux kernel to create only one ttyUSB device for
-# such USD IDs.
-#
-# What follows is a dump of the EEPROM made from the debug board which
-# I got with my FreeRunner back in 2011; it appears to have a per-unit
-# serial number string.  The FTDI chip is FT2232D and the EEPROM is a 93C56.
-
-00: 0802 1457 5118 0500 3280 0000 0200 1296
-10: 30A8 12D8 0056 0000 0000 0000 0000 0000
-20: 0000 0000 0000 0000 0000 0000 0000 0000
-30: 0000 0000 0000 0000 0000 0000 0000 0000
-40: 0000 0000 0000 0000 0000 0000 0000 0000
-50: 0000 0000 0000 0000 0000 0000 0000 0000
-60: 0000 0000 0000 0000 0000 0000 0000 0000
-70: 0000 0000 0000 0000 0000 0000 0000 0000
-80: 0000 0000 0000 0000 0000 0000 0000 0000
-90: 0000 0000 0000 0312 004F 0070 0065 006E
-A0: 004D 006F 006B 006F 0330 0044 0065 0062
-B0: 0075 0067 0020 0042 006F 0061 0072 0064
-C0: 0020 0066 006F 0072 0020 004E 0065 006F
-D0: 0031 0039 0037 0033 0312 0046 0054 0053
-E0: 0048 0044 004E 0032 004B 0000 0001 0000
-F0: 0000 0000 0000 0000 0000 0000 0000 773F
diff -r 17ffa6c66951 -r f9ca05460238 eeproms/dumps/usb-com232-plus2
--- a/eeproms/dumps/usb-com232-plus2	Mon Sep 11 04:17:09 2023 +0000
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,24 +0,0 @@
-# USB-COM232-PLUS2 is a board made by FTDI based on their FT2232H chip.
-# It is an adapter going from USB to two physical RS-232 ports on DE9M
-# connectors, thus it is a vanilla dual-UART device with the standard
-# 0403:6010 USB ID, but it still has an EEPROM (93C56) in which custom
-# textual ID strings have been programmed: the product string is
-# "USB-COM232 Plus2" instead of chip-default "Dual RS232-HS", and there
-# is a serial number string.
-
-00: 0808 0403 6010 0700 6480 0008 0000 0A9A
-10: 22A4 12C6 0000 0000 0056 0000 0000 0000
-20: 0000 0000 0000 0000 0000 0000 0000 0000
-30: 0000 0000 0000 0000 0000 0000 0000 0000
-40: 0000 0000 0000 0000 0000 0000 0000 0000
-50: 0000 0000 0000 0000 0000 0000 0000 0000
-60: 0000 0000 0000 0000 0000 0000 0000 0000
-70: 0000 0000 0000 0000 0000 0000 0000 0000
-80: 0000 0000 0000 0000 0000 0000 0000 0000
-90: 0000 0000 0000 0000 0000 030A 0046 0054
-A0: 0044 0049 0322 0055 0053 0042 002D 0043
-B0: 004F 004D 0032 0033 0032 0020 0050 006C
-C0: 0075 0073 0032 0312 0046 0054 0057 0055
-D0: 004C 0052 0054 004D 0302 0001 0000 0000
-E0: 0000 0000 0000 0000 0000 0000 0000 0000
-F0: 0000 0000 0000 0000 0000 0000 0000 BE30