New Contributor
New ContributorJohnT as stated above: the "real" driver must be the standard Linux generic USB driver, jtagd will "probably" use a user level API layer like libusb to communicate with the Linux driver. There is no driver for Linux in the Quartuis distribution as far as i am aware, or is there one we can use ? I have configured udev to allow access to this driver for the vendor/product USB ID's as per the Intel installation instructions. Linux provides a generic USB driver used for applications like this, it is not Microsoft Windows.
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!
