[fprint] Match-on-chip device by PixelAuth - model Primex

[Furkan Salman]

Hello Benjamin,


Thank you for the reply.


Currently Merlin from PixelAuth have completed the drivers which makes use of the device storage. The issue we had was we could only enroll single user fingerprints and if any other users tries to enroll the same fingerprint then it would overwrite the previous one.

Merlin have found a way to get around it.

You can find a working drivers on your git
https://gitlab.freedesktop.org/llforce/libfprint/-/commits/pa_primex



It will be helpful if you can have a look at it and share your feedback, we do plan to push it upstream but it needs some cleaning.



For the samples, I will contact Merlin and get back to you, as Me and Philip Muller are part of Manjaro Linux community and we have a plan to release Beelink GTR with Manjaro Linux pre-installed and GTR have this fingerprint reader in it.


Regard,
Furkan Kardame
Manjaro Linux.

---- On Wed, 07 Oct 2020 13:11:03 +0300 Benjamin Berg <mailto:benjamin at sipsolutions.net> wrote ----


Hi Furkan (and anyone at PixelAuth), 
 
On Tue, 2020-09-15 at 16:44 +0300, Furkan Salman wrote: 
> I have been working with PixelAuth developer who have a new 
> fingerprint sensor with match-on-chip with storage capacity of 16 
> fingers. 
 
Sorry if I didn't have a closer look at the code yet. 
 
> We have been able to get a working open source driver for it but 
> there is a need to find a standard to have match-on-chip for multiple 
> user with similar fingers enrolled. 
> 
> Might need help in understanding how multi user with similar 
> fingerprint can be implemented and also a way to delete only selected 
> fingerprint of a given user as currently it deletes all fingerprint 
> in the device. 
> 
> Here is the git for working driver. 
> https://gitlab.freedesktop.org/llforce/libfprint/-/tree/pa_primex 
> 
> If anyone can look into this and help with missing stuff. 
 
I can take a look, feel free to just send me a reminder if forget. 
Also, feel free to reach out to me in private if there is anything that 
you cannot discuss openly. 
 
 
Could you explain to me what the storage code is for? You really 
shouldn't be needing any storage code within the libfprint driver. The 
libfprint API user (i.e. fprintd) will take care of this for you. 
 
It looks to me like you are trying to solve problems in the driver that 
are better handled by libfprint or fprintd (and may be solved already 
there). 
 
 
Other than that, is PixelAuth able to provide a couple of samples for 
the current maintainers of the project (one goes to me at Red Hat and 
the other would go to Marco at Canonical)? 
I'll provide shipping information in private then. 
 
Benjamin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/fprint/attachments/20201008/d216df6d/attachment.htm>