Forum Discussion
Ok, some more information. Ok, there is a kernel driver and API library in that directory although this does not appear to be used. The driver would only build for up to 2.6.x kernels which are very very old (~2005 !). Our Fedora systems use the 4.20.14 and RedHat 7.5 3.10.0. That directory seems like a historical driver for very very old legacy systems. As stated earlier i strongly suspect that jtagd uses the libusb/generic Linux USB driver.
But again, as stated above, "Given my further debugging of the issue in the Intel jtagd program, as listed above, it appears it is more of a general internal memory pointer bug in jtagd not related to the USB driver but possibly due to underlying system updates. It would have taken me 10 minutes to find this bug in the jagd source code!"