Technical Document #8: When trying to install WinDriver v5.2.0 on my PC, using the Linux RedHat 7.2 distribution, I got unresolved symbol errors pertaining to alloc_kiovec() and free_kiovec(). How can I resolve these errors?

These errors are due to a change in the alloc_kiovec() andfree_kiovec() functions in the Linux RedHat 7.2 distribution.
In version 5.2.2 of WinDriver we have modified the WinDriver Linux makefile (WinDriver/redist/makefile) in order to eliminate this error, by setting the value of KIOBUF_WITH_SIZE in the makefile according to the Linux distribution that is being used. When using version 5.2.0 or 5.2.1 of WinDriver, you can resolve this error by changing the value of KIOBUF_WITH_SIZE in the makefile (WinDriver/redist/makefile) from 0 to 1 and then rebuild the code (as documented in the makefile itself — Ln28):

We use WinDriver PCI for 32-bit Windows, 64-bit Windows, 32-bit x86 Linux, and 64-bit x86 Linux. We have also used it for 32-bit x86 Solaris and 64-bit SPARC Solaris. This tool kit allows us to use a common driver interface for these platforms and greatly simplifies our software API architecture. Basic driver is very easy, advanced features like the kernel plug-in allow optimization of interrupt handling, etc.

Rich WadeAlta Data Technologies

The WinDriver worked out well for us. It took very little time to get the driver working. We have implemented DMA and interrupt.

Tak-kwong NgElectronics Engineer | NASA Langley Research Center

I started using the WinDriver Kit after looking at several other possibilities. All others that I looked at were targeted for Software Engineers with deep background on driver development, which for me being hardware-centric was a big obstacle. When I found the Jungo Tools I initially looked at the online video showing how to drive the kit. When I tried out the real software I was amazed that within ten minutes I had my first driver working and could interact with my custom FPGA-based board.