[fprint] Call for testing: UPEK 147e:1001, AES1660, AES1610, AES2501, AES2550, AES2810, AES2660

[Julian Sikorski]

Hi Vasily,

I don't know if it times out every time, but the results look the same
from the user perspective.
How do I know fprint_demo is ready for enrollment, and that I should
continue with re-scanning the finger?

Best regards,
Julian

W dniu 20.03.2014 09:04, Vasily Khoruzhick pisze:
> Hi Julian,
> 
> According to log, it looks like one control transfer (write reg) of
> deinit sequence timed out. Does it happen all the time?
> 
> Please note, that with latest changes all imaging devices do 5 scans
> for enrollment.
> 
> Regards
> Vasily
> 
> On Thu, Mar 20, 2014 at 9:13 AM, Julian Sikorski <belegdol at gmail.com> wrote:
>> W dniu 16.03.2014 11:45, Vasily Khoruzhick pisze:
>>> Hi to all fingerprint scanner users,
>>>
>>> It's another call for libfprint testing.
>>>
>>> Good news to all UPEK 147e:1001 users - I've added support for that
>>> device into upeksonly driver - so it worth testing. It also may work
>>> for 147e:1002 device - just try to add its USB IDs into upeksonly.c
>>> and use UPEKSONLY_1001 variant for it.
>>>
>>> Also I've improved image assembling utilities for all AuthenTec
>>> scanners, so now match rate is a bit better for AES1660 scanner - so
>>> all AES1660 are encouraged to test my changes as well.
>>>
>>> All changes are pushed into master branch of
>>> git://github.com/anarsoul/libfprint.git repo.
>>>
>>> To obtain the code do:
>>>
>>> git clone git://github.com/anarsoul/libfprint.git
>>>
>>> Use instructions from [1] to compile and test it. Thanks!
>>>
>>> Regards,
>>> Vasily
>>>
>>> P.S. PLEASE KEEP FPRINT MAILLIST IN CC!
>>>
>>> [1] http://lists.freedesktop.org/archives/fprint/2012-November/000330.html
>>>
>> Hello,
>>
>> 147e:1001 does not seem to be working here. When I open fprint_demo and
>> pick a finger to enroll, the child window shows nothing for a while.
>> When I scan my finger regardless, a scan will appear at some point, but
>> with a message "enrollment failed due to bad scan data, press cancel to
>> continue". Logs attached.
>>
>> Best regards,
>> Julian