[fprint] Willing to write driver for LightTuning Fingerprint Reader

[Yujie REN]

Thanks for all your replies and suggestions. I'm gonna read the source code
of libfprint and try to understand how libfprint works first.

--------------------------------------------------------------------
Thanks,
Yujie REN
M.S. Student of Computer Science Department
Rutgers University
--------------------------------------------------------------------

On Fri, Mar 10, 2017 at 12:55 PM, Vasily Khoruzhick <anarsoul at gmail.com>
wrote:

> On Fri, Mar 10, 2017 at 7:26 AM, Carson Reinke <carson at reinke.co> wrote:
> > As a starting point, take a look at the source libfprint/drivers to see
> each
> > driver for the appropriate device.  Not sure if the authors have actually
> > referenced the devices SDK or if there was some reverse engineering.  It
> > might not hurt to try and hit them up on email to see.  I would imagine
> the
> > devices share some common concepts.
>
> There was *some* reverse engineering for most devices. Currently we
> support 3 types of devices in libfprint:
>
> 1) Devices that provide whole image at once, i.e. no assembly needed.
> These can be swipe or touch sensors. See
> libfprint/drivers/upektc_img.c as example.
> 2) Authentec-like devices: these are swipe devices, they provide short
> frames, e.g. 192x4, driver has to assemble them,
> we have routines for movement estimation and assembly in libfprint,
> see libfprint/drivers/aes2550.c for example
> 3) validity-like devices (vfs5011): these are swipe devices, but they
> provide only one full line per frame (e.g. 192x1) and shorter next
> line (64x1 at the image center),
> driver has to do movement estimation and assembly, we have routines to
> do that, see libfprint/drivers/vfs5011.c or
> libfprint/drivers/upeksonly.c for example.
>
> >
> > Please share what you come up with!
> >
> > On Thu, Mar 9, 2017 at 12:16 PM, Yujie REN <renyj1991 at gmail.com> wrote:
> >>
> >> Hello,
> >>
> >>     I recently bought a Acer Swift 3 with a LighTuning Fingerprint
> reader,
> >> the ID is 1c7a:0570. The only available driver is for 0603 not for
> 0570. So,
> >> I'm gonna write a driver by myself.
> >>
> >>     As a Linux user, and a computer science student in system track, I
> >> have solid foundation in C programming, Operating System and Assembly.
> Since
> >> I don't have experience in open source development, it'll be
> challenging for
> >> me, but I'd like to join. I'll have time for this project, could anybody
> >> give me some suggestions to start with?
> >>
> >> --------------------------------------------------------------------
> >> Thanks,
> >> Yujie REN
> >> M.S. Student of Computer Science Department
> >> Rutgers University
> >> --------------------------------------------------------------------
> >>
> >> _______________________________________________
> >> fprint mailing list
> >> fprint at lists.freedesktop.org
> >> https://lists.freedesktop.org/mailman/listinfo/fprint
> >>
> >
> >
> > _______________________________________________
> > fprint mailing list
> > fprint at lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/fprint
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/fprint/attachments/20170310/aa91f2f6/attachment-0001.html>