Hi all,
attached latest version of the patch that fix the issue reported to me.
The changes are important and needs to be re-tested for avoid
regressions.
I ask to anybody test the patch if can send me the feedback (positive or
negative).
Bye
Sergio
Il giorno ven, 25/02/2011 alle 09.49 +0100,
On Thu, 2011-03-03 at 10:46 +0100, Sebastian Pöhn wrote:
Hi Sergio!
Thanks for your work on the Validity device. I own a VFS300. I used
your patch and added some code to accept my device (138a:0008).
The protocol is at least not exactly the same as VFS101. Could you
please send me a usb
Hi Ymhuang,
isn't so good. The patch i send to you are only for debug and break the
image quality of many other reader.
Now, not all sensor have same behavior and, like as windows drivers, is
necessary to implement an auto calibration of the device.
Could you done one test for me ?
If yes, try
Hi Sebastian,
sorry but i haven't it. My patch is based on Rayl work.
See the follow link if you can found anything:
https://github.com/rayl/vfs101driver
Bye
Sergio
Il giorno gio, 03/03/2011 alle 10.46 +0100, Sebastian Pöhn ha scritto:
Hi Sergio!
Thanks for your work on the Validity
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 will fix the
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
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
Hi Kunal,
i have done some test and reproduce the first issues (image height = 1).
Removing the break isn't correct because without it empty lines at end
of finger image are not removed. I rewrite a logic of first block of
img_screen and now is more robust.
I can't reproduce the second issue, on
Hi Kunal,
thank for feedback and patch.
I will investigate on the two issues, could you send me the log ?
The issues you report are occasional or systematic ?
Bye
Sergio
Il giorno dom, 27/02/2011 alle 16.20 +0530, Kunal Gangakhedkar ha
scritto:
Hi Sergio,
Awesome work !!
Got the patch
On Sunday 27 Feb 2011 3:35:18 pm Sebastian Pöhn wrote:
I got the VFS101 patch, but have a VFS300 (138a:0008). I added its
usb-id in vfs101.c , but the device is not detected at all! Is there an
other place where I need to add it?
What's the error?
If you get a 'Permission Denied' message,
On Fri, 25 Feb 2011 09:49:23 +0100
Sergio Cerlesi sergio.cerl...@gmail.com wrote:
Hi all,
i finish to write the driver fo Validity VFS101. I use it for a couple
of day with good result.
For verify the implementation i need tester. If i receive positive
feedback i will work to merge it
11 matches
Mail list logo
