Alexia Death 25161286f5 Only complete scan with MIN_ROWS in print ...

Don't consider the scan complete unless theres at least
MIN_ROWS recorded or very long blank read occurred.

Typical problem spot: one brief touch before starting the
actual scan. Happens most commonly if scan is started from
before the first joint resulting in a gap after the inital touch.

http://lists.reactivated.net/pipermail/fprint/2009-December/001406.html

2010-08-19 20:36:16 +01:00

..

aes1610.c

Finish implementation of AES1610 driver

2010-08-17 11:36:34 +01:00

aes2501.c

Export scan type for each driver

2008-11-20 14:53:01 +00:00

aes2501.h

Add AES2501 driver

2007-11-15 09:54:39 +00:00

aes4000.c

Export scan type for each driver

2008-11-20 14:53:01 +00:00

fdu2000.c

Export scan type for each driver

2008-11-20 14:53:01 +00:00

upeke2.c

Implement discover() methods for upeke2 and upeksonly

2010-08-17 23:41:23 +01:00

upeksonly.c

Only complete scan with MIN_ROWS in print

2010-08-19 20:36:16 +01:00

upektc.c

Export scan type for each driver

2008-11-20 14:53:01 +00:00

upekts.c

upekts: Don't choke on non-zero bytes in command response

2008-11-20 19:59:43 +00:00

uru4000.c

Export scan type for each driver

2008-11-20 14:53:01 +00:00

vcom5s.c

Export scan type for each driver

2008-11-20 14:53:01 +00:00