Hi, The attached patch fixes the demo driver.
When initialized, the driver starts a thread that generates signal datas. These data are writen them to a pipe (write file descriptor). The other end of the pipe (read file descriptor), is connected to the main polling code, like any other driver. Note this patch adds a new dependancy with libgthreads. At the moment, you can list the driver's device: ./cli/sigrok-cli -D The following devices were found: ID Device 0 Sigrok project Demo Driver v1.0 with 8 probes And use it for random signal generation [oliv...@cooper sigrok]$ /opt/sigrok/bin/sigrok-cli -d 0 --samples 50 -f bits -p 1-8 sigrok 0.1pre2 Acquisition with 8/8 probes at 0 Hz 1:10111100 11010110 00001011 00011110 00111010 11110100 10 2:11010110 00111111 01001010 11111101 11010011 00010010 11 3:11000101 01000001 10100011 10100100 10110000 11110011 00 4:00100111 11110100 10011101 01100111 00100101 01001110 10 5:00011100 00101100 10111000 11001101 01011101 01011011 01 6:10110101 10111110 10010110 10111000 11011010 10000100 11 7:11111111 01001111 11110110 11010010 10000101 01001111 00 8:01000101 01111110 01010111 00000111 00010010 00000101 11 Next step is to make demo driver customisable (per-probe signal clock, reference sample signals : serial, i2x, can...) -- Olivier Fauchon www.oflabs.com ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
