From: David R. <Mail@DavidRoberts.Org.UK> - 2014-06-11 20:47:51
|
Greetings. I have recently discovered sigrok, so I am a new member of the mailing list. I have several questions which I am putting into separate threads. This is the third. Related to my enquiry about possible support for the DPScopeSE/pcbscope. I have set out on an attempt to write my own hardware driver for a DPScopeSE. Scanning through other supported devices, it seems that the IKALOGIC Scanalogic-2 is also an HID based device that I might use as a model for hacking a new driver. So I 'cloned' ~/libsigrok/hardware/ikalogic-scanalogic2/ into ~/libsigrok/hardware/dpscopese/ and changed all the relevant defines to contain new identification strings, and changed the usb identity of the target device. But then I hit a brick wall. I could not work out how to include my new 'dpscopese' source code in the build-process, and I can't find any documentation that explains this. I assume it must be some input to autogen.sh or configure that generates a new Makefile, but I can't see how... can someone enlighten me, please? Regards - David Roberts |
From: Matthias H. <m-s...@he...> - 2014-06-11 21:12:52
|
Hi David, Am 11.06.2014 um 22:47 schrieb David Roberts <Mail@DavidRoberts.Org.UK>: > I have set out on an attempt to write my own hardware driver for a DPScopeSE. Scanning through other supported devices, it seems that the IKALOGIC Scanalogic-2 is also an HID based device that I might use as a model for hacking a new driver. > > So I 'cloned' ~/libsigrok/hardware/ikalogic-scanalogic2/ into ~/libsigrok/hardware/dpscopese/ and changed all the relevant defines to contain new identification strings, and changed the usb identity of the target device. > > But then I hit a brick wall. I could not work out how to include my new 'dpscopese' source code in the build-process, and I can't find any documentation that explains this. I assume it must be some input to autogen.sh or configure that generates a new Makefile, but I can't see how... can someone enlighten me, please? The best way to do it is to use the script new-driver in sigrok-util/source. It creates a patch that can be applied with git. If you want to do it manually, I think you need to add it to the following places: - Makefile.am - configure.ac - hwdriver.c It’s best to grep for an existing driver to find all the places in these files that need to be changed. Bye, Matthias |