[fprint] New driver for Validity VFS101: tester wanted

Sergio Cerlesi sergio.cerlesi at gmail.com
Wed Mar 2 12:42:30 GMT 2011


Hi Kunal,

the program on example directory (like fprint_demo and pam_fprint)
receive the result and re-call the action if not completed.

The daemon fprintd (and fprintd-verify) when receive "remove finger"
result wait for another image without re-call the action.

Try the new patch. It seem to work with all these program.

Bye
Sergio

Il giorno mer, 02/03/2011 alle 17.13 +0530, Kunal Gangakhedkar ha
scritto:
> On Wednesday 02 Mar 2011 2:38:40 pm Sergio Cerlesi wrote:
> > Hi Kunal,
> > 
> > thank for logs. I found and successful reproduced the second issue.
> > 
> > Seem to be a bug of driver that appear when it are called from a program
> > that not handle "remove finger" result like fprint_demo or pam_fprint.
> > With fprintd and pam_fprintd the bug are not present.
> > 
> 
> I wasn't using either of these programs.
> I was using the ones under libfprint/examples - enroll and verify.
> 
> These seem to handle the 'remove finger' result because they show the message like 'Please remove finger from sensor'.
> For example, this is the code from libfprint/examples/enroll.c (line 83):
> 
>         case FP_ENROLL_RETRY_REMOVE_FINGER:
>             printf("Scan failed, please remove your finger and then try "
>                 "again.\n");
>             break;
> 
> So, it seems to handle it.. :)
> 
> Kunal
> 
> > I will fix the driver.
> > 
> > Bye
> > Sergio
> > 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: libfprint-0.3.0-vfs101.v3.patch
Type: text/x-patch
Size: 36153 bytes
Desc: not available
Url : http://lists.reactivated.net/pipermail/fprint/attachments/20110302/f1904f0c/libfprint-0.3.0-vfs101.v3-0001.bin


More information about the fprint mailing list