Code: Select all
file Panalyzer Panalyzer: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=0x0ac8c9951674961e9524164ec990bec740a762bc, not stripped
Code: Select all
pandriver: no symbol version for module_layout pandriver: no symbol version for module_layout No module found in object pandriver: no symbol version for module_layout pandriver: no symbol version for module_layout
I am not sure if it is possible.rgh wrote:I did briefly look in to using DMA, but I wasn't able to find a way of pacing the DMA requests at a steady rate. ......
Yeah, it is a bit lacking in that area at the moment. Basically it comprises two parts, a kernel module and a user space UI. The kernel module needs compiling against the correct kernel. I followed the wiki instructions to cross-compile the kernel on my 64 bit Ubuntu box. Once you have a compiled kernel tweak the Makefile appropriately to set the path to the kernel and whatever you need for the ARCH and compiler prefix, if cross-compiling, and then type 'make pandriver.ko'. You also need to 'make Panalyzer' for the user space part; I tend to cross-compile the module but build the UI on the Pi itself. Anyway, then follow the notes at the top of pandriver.c to get the system to create the /dev/pandriver device node automatically when the module is loaded, and finally, as root, 'insmod pandriver.ko'. You might well need to install extra packages to get the UI to compile. For example, "apt-get install pkg-config libgtk2.0-dev".higwoth1 wrote:Looks very good, would be nice if it had some docs on compiling it, so I could try it out.
Users browsing this forum: OutoftheBOTS and 15 guests