comparison doc/Unbuffered-FT2232x-JTAG @ 81:bbeec8f293dc

FC JTAG+UART ftdi_sio patch made it to stable
author Mychaela Falconia <falcon@freecalypso.org>
date Sun, 18 Oct 2020 22:26:46 +0000
parents 1d38af6d7be8
children 4f5abad5dd40
comparison
equal deleted inserted replaced
80:1d38af6d7be8 81:bbeec8f293dc
82 the unbuffered JTAG adapter configuration. 82 the unbuffered JTAG adapter configuration.
83 83
84 Support for this 0403:7151 USB ID has been added to Linux ftdi_sio driver in 84 Support for this 0403:7151 USB ID has been added to Linux ftdi_sio driver in
85 2020-09 with this commit: 85 2020-09 with this commit:
86 86
87 https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git/commit/?id=6cf87e5edd9944e1d3b6efd966ea401effc304ee 87 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6cf87e5edd9944e1d3b6efd966ea401effc304ee
88 88
89 This commit is not included in Linux 5.9, but is expected to appear in the 89 This commit is included in stable kernel versions 4.4.240, 4.9.240, 4.14.202,
90 mainline tree as of 5.10-rc1. If your Linux kernel version (or rather ftdi_sio 90 4.19.152, 5.4.72, 5.8.16 and 5.9.1, and it will appear in mainline kernels from
91 driver version if it's a module) includes this commit, the ftdi_sio driver will 91 5.10 onward. If your Linux kernel version (or rather ftdi_sio driver version
92 create a ttyUSB device for Channel B, allowing that channel to function as a 92 if it's a module) includes this commit, the ftdi_sio driver will create a
93 UART if desired, but Channel A will be left alone by the kernel driver, reserved 93 ttyUSB device for Channel B, allowing that channel to function as a UART if
94 for userspace applications like OpenOCD. If your kernel/driver version does not 94 desired, but Channel A will be left alone by the kernel driver, reserved for
95 userspace applications like OpenOCD. If your kernel/driver version does not
95 include the newly added commit, both FT2232x channels will be left alone by the 96 include the newly added commit, both FT2232x channels will be left alone by the
96 kernel driver, i.e., no ttyUSB devices will be created. If you are interested 97 kernel driver, i.e., no ttyUSB devices will be created. If you are interested
97 only in JTAG and don't need an extra UART on Channel B, it should not matter 98 only in JTAG and don't need an extra UART on Channel B, it should not matter
98 whether your ftdi_sio driver knows about the new custom USB ID or not - you 99 whether your ftdi_sio driver knows about the new custom USB ID or not - you
99 simply configure your OpenOCD in userspace to find your unbuffered and ad-hoc- 100 simply configure your OpenOCD in userspace to find your unbuffered and ad-hoc-