The upeksonly device seems to work *very* differently to the other two
devices. The upeksonly driver has not the same structure as the upekts
driver as well, and we should need to take a very deep look into its
code to do the matching. I mean, that would be a lot of hard work.
I like your idea,
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
On 04/26/2010 02:33 PM, Jorge Suárez de Lis wrote:
That's weird. I've never received 2e. You should receive 0d, then 0e,
then 26 and then 27. But not 2e.
Is your device the same as mine? On the barcode it says TCRD4CA1H6A3.
Try this, after line 1000 (case 0x27:) add this:
I can't check
Full lsusb output:
Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip
Fingerprint Sensor
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.01
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0
