comedilib

History

Ian Abbott 9683559f51 comedi_test: fix test_cmd_write_fast_1chan() for big buffer If the comedi data buffer is larger than the total size of the data being written to the buffer in first test_cmd_write_fast_1chan(), the first loop iterates endlessly writing 0 bytes to the buffer. Break out of the first loop once the required amount of data has been written.		2014-04-10 20:19:43 +01:00
..
results	new files	2003-11-20 18:40:30 +00:00
bufconfig.c	additional tests, fixes, move some functions to ../lib	2001-05-28 02:39:00 +00:00
cmd_1.c	comedi_test: fix test_cmd_write_fast_1chan() for big buffer	2014-04-10 20:19:43 +01:00
cmd_2.c	Don't use SDF_WRITEABLE flag to check if read (or write) command is	2008-01-28 16:10:11 +00:00
cmd_3.c	Fixed comedi_get_cmd_generic_timed() by adding a chanlist_len	2007-08-02 19:46:44 +00:00
comedi_test.h	comedi_internal_trigger is provided by comedilib now.	2008-01-28 20:38:47 +00:00
info.c	Handle COMEDI_SUBD_PWM and check for future unknown subdevice types.	2008-11-05 11:40:42 +00:00
insn_read.c	test reading 0 samples	2002-06-06 00:38:54 +00:00
insn_read_time.c	Fix use of INSN_GTOD so it works on 64-bit platforms.	2007-11-07 13:01:50 +00:00
inttrig.c	comedi_internal_trigger is provided by comedilib now.	2008-01-28 20:38:47 +00:00
lib.c	staging area for moving functions from here to ../lib	2001-05-28 02:38:09 +00:00
main.c	testing: remove unused variables in comedi_test program	2013-05-07 13:15:54 +01:00
Makefile.am	need headers	2003-05-02 07:53:02 +00:00
mmap.c	testing: remove unused variables in comedi_test program	2013-05-07 13:15:54 +01:00
mode0_read.c	fix for compiler warning about strict aliasing rules	2004-06-19 19:55:26 +00:00
README	testing additions	2000-11-30 22:57:04 +00:00
select.c	Don't use SDF_WRITEABLE flag to check if read (or write) command is	2008-01-28 16:10:11 +00:00

README

The results directory contains last-known testing results that have
been contributed by users.  If your board is listed there,
please compare it the output of comedi_test and if it differs
significantly, send me a copy and/or diff.  I'll either update
the file, or it indicates that there is a bug.  If your board
is not listed here, send me a copy of the output so it can
be included.

comedi_test tends to create a lot of output.  The important
information has lines beginning with either I:, W:, or E:,
indicating information, warning, or error, respectively.
You can grep for this information using the regexp '^.:'.
Errors are usually problems that need to be fixed, but are
not necessarily significant bugs.  Warnings need to be
audited by ds to know whether or not they are significant,
since comedi_test isn't very smart about some checks.  (That's
why they're warnings and not errors.)