I don't think there's any way to do this on fprint. I still have to take
a better look at the code, but it seems that the drivers just register
themselves as I am ready to support the device with these IDs, so I'll
do the job.
I have an upeksonly device. It must be possible to differentiate
a190a2ee2e21b794596979d1e19eb555ab5ceb91 Mon Sep 17 00:00:00 2001
From: Alexia Death alexiade...@gmail.com
Date: Sat, 26 Dec 2009 17:02:03 +0200
Subject: [PATCH 1/2] Dont consider the scan complete unless there is atleast MIN_ROWS of print or a long gap
Typical problem spot: one brief touch before starting the actual scan
