Alright, I think I finally got somewhere.
I can run img_capture successfully. I see two pgm files in my directory
that look like fingerprints.
This particular device can’t do the matching so it all has to be done on
the host.
I assume libfprint can do this?
I can’t seem to run enroll. This is th
Not really. The same state is sent to dev_change_state after activation has
ended with fpi_imgdev_activate_complete. You can ignore it.
On Fri, Mar 9, 2018 at 8:51 PM Mark Harfouche
wrote:
> Hi Igor,
>
> Thank you for your reply.
>
> I’m confused about the parameter sent to dev_activate. Is it
Hi Igor,
Thank you for your reply.
I’m confused about the parameter sent to dev_activate. Is it useful? in
uru4000.c (which seems to be the latest one written), the authors also seem
to be confused
/* FIXME: having state parameter here is kinda useless, will we ever
* see a scenario where the p
Hi Mark,
There are no high-level docs, unfortunately. There's some valuable info in
comments in drv.c, sync.c, async.c, img.c etc. but it only covers specific
parts, not how they should interact.
There are 6 drivers for press-type sensors: aes3500.c, aes4000.c,
fdu2000.c, upektc.c, uru4000.c, vco
Hello all,
I would like to develop a driver for the Validity 0091 sensor available on
the Dell XPS13/15 9X60.
I would say I have the driver reverse engineered to 95% (There might be a
few things I still don’t understand from the internal state machine).
https://github.com/hmaarrfk/Validity91
WIP:
