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

Benjamin Berg benjamin at sipsolutions.net
Thu Oct 8 16:20:46 UTC 2020


Hi Furkan,

On Thu, 2020-10-08 at 18:31 +0300, Furkan Salman wrote:
> 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.

Hmm, yeah, that is the same version that I looked at. And the storage
part really needs to be solved differently. But I am not sure how the
reader works or why the code is written in the way it is.

> 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.

Right, maybe it would be good if I talk to Merlin/PixelAuth directly?

Then we can maybe also figure out how to get the driver into a
mergeable state.
If it helps, I am also happy for us to have a call to discuss
everything.

Benjamin

> ---- On Wed, 07 Oct 2020 13:11:03 +0300 Benjamin Berg <
> 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 
> 
> 
> _______________________________________________
> fprint mailing list
> fprint at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/fprint
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/fprint/attachments/20201008/399f34dd/attachment.sig>


More information about the fprint mailing list