Bug 90964 - Add support for validity 138a:0010 reader
Summary: Add support for validity 138a:0010 reader
Status: RESOLVED MOVED
Alias: None
Product: libfprint
Classification: Unclassified
Component: libfprint (show other bugs)
Version: unspecified
Hardware: Other All
: medium enhancement
Assignee: libfprint-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-13 08:04 UTC by Bartosz
Modified: 2018-05-31 08:56 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments
adapt VFS5011 driver to 138a:0010 device (1.73 KB, text/plain)
2015-06-13 08:04 UTC, Bartosz
Details

Description Bartosz 2015-06-13 08:04:51 UTC
Created attachment 116469 [details]
adapt VFS5011 driver to 138a:0010 device

Validity 138a:0010 sensor is present in some Toshiba laptops (my model Toshiba Portege Z30). Driver VFS5011 supports other validity devices and seems to work with 0010 reader after adding its ID to the list of supported devices.

The attached patch contains all the changes required to make VFS5011 work with my reader. I had to tweak the parameters to have a reliable fingerprint matching (works in 75% of matching trials). It is NOT meant to be merged in the upstream, because it will likely break support for other readers. What is the best way to handle this small differences in parameter settings in libfprint drivers?
Comment 1 Vasily Khoruzhick 2015-11-24 23:24:58 UTC
Hi, could you please check that libfprint from vfs5011-0010 branch of this repo: https://github.com/anarsoul/libfprint works for you? Thanks!
Comment 2 amit.prakash.ambasta 2016-03-15 13:17:30 UTC
Hey,

I am on 1381:0010.. and while I can verify that the specified branch does detect the fingerprint reader ( and requests for 5 scans for finger ), it fails on validating the fingerprint every single time (while using fprint_demo)
Comment 3 amit.prakash.ambasta 2016-03-15 13:18:01 UTC
Sorry, the device is 138a:0010
Comment 4 GitLab Migration User 2018-05-31 08:56:14 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/libfprint/libfprint/issues/53.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.