[fprint] elan patch + poc 0x903 and 0x0C03

Wed Jan 17 18:21:08 UTC 2018

We didn't have the spec before so I had no idea how different devices
worked. Especially given that some commands which worked fine for me
produced errors one other devices. Now that we have the docs I'll work on
adapting the driver. Naturally, any info you have is welcome and so is any
help with testing.

On Wed, 17 Jan 2018, 20:13 TeEmZe, <timo at teemze.de> wrote:

> Hi,
>
> I now logged the communication of the Windows driver in a VM on the Xiaomi
> Laptop with the fingerprint sensor 04F3:0C1A. It seems to use nearly the
> same commands as stated in the documentation Hans got. That means, I logged
> the process of enrolling a new fingerprint. Here it firstly send a 4031 (I
> don't know what that one does, as I couldn't find it in the commands doc
> Hans found), then a 403F (Pre-Scan), the device answered with 55 (object),
> then again the driver sent 4031, then 0009 (GET Image Data), to which the
> device probably answered with the image data. This repeated a few times and
> at the end the driver sent 000B (Stop).
>
> I don't know, how valuable this information is for you. Igor told me about
> a week ago, that I should build the driver on my own, but now you all seem
> to be into the development of a driver which works for me too. Is it even
> logical anymore for me to develop one on my own? And if not, can I be
> helpful otherwise, maybe with testing?
>
> I'd appreciate some response.
>
> Regards,
>
> Timo
>
> -----Original Message-----
> From: fprint [mailto:fprint-bounces at lists.freedesktop.org] On Behalf Of
> Hans de Goede
> Sent: Wednesday, 17 January 2018 16:26
> To: Igor Filatov <ia.filatov at gmail.com>
> Cc: fprint at lists.freedesktop.org; Sébastien Béchet <
> sebastien.bechet at osinix.com>
> Subject: Re: [fprint] elan patch + poc 0x903 and 0x0C03
>
> Hi,
>
> On 17-01-18 16:22, Igor Filatov wrote:
> > For me this is either 0x01 or 0x03, just like in the docs. But I do
> remember that I could never make it behave like Windows driver did, e.g.
> return same values when I sent the same commands in the same order. But I
> didn't know I had to give it some time, so that could be the problem.
> >
> > And I've never seen the Win driver do reset or fuse load. I wonder
> what's it for...
>
> Right, I don't think those are necessary.
>
> Regards.
>
> Hans
>
>
>
> >
> > On Wed, Jan 17, 2018 at 4:59 PM Hans de Goede <hdegoede at redhat.com
> <mailto:hdegoede at redhat.com>> wrote:
> >
> >     Hi,
> >
> >     On 17-01-18 14:46, Sébastien Béchet wrote:
> >      > Hello,
> >      >
> >      > I have done more test and find a functionnal calibration method.
> >      >
> >      > Strangely, the calibration return returns Mean_H and not the
> expected status. I need to read the "FP Status" register for the
> calibration to work in the next step.
> >      >
> >      > Also, i added 0x04f3:0x01cA to the test list.
> >      >
> >      > Hans, can you help us to find a recent list of ids?
> >      >
> >      > All work now for me:
> >      >
> >      > $ sudo ./elanfp
> >      > Device with vid 4f3 pid 903 found.
> >      > Config number is 1
> >      > CMD RESET sent
> >      > CMD Fuse Load sent
> >      > CMD VERSION sent
> >      > FP Bridge FW Version 1.53
> >      > CMD Get Image Size sent
> >      > width x height = 96x96
> >      > CMD Get Calibration Mean sent
> >      > calibration mean value: 33792 (0x8400)
> >      > CMD CALIBRATION sent
> >      > Calibration Status: 0x84
> >
> >     So for me, this is actually 0x03 and if I don't
> >     add a break condition on this being 0x03 then
> >     the code never leaves the calibration loop for me,
> >     keep in minds that I asked Elan for docs for
> >     *my* model fingerprint reader, although all these
> >     are alike they are not 100% the same...
> >
> >     With that all said, good job! With this one small
> >     change the program works for me.
> >
> >     Regards,
> >
> >     Hans
> >
> >
> >      > CMD STATUS sent
> >      > Status: 0x1
> >      > CMD Get Calibration Mean sent
> >      > calibration mean value: 256 (0x100)
> >      > CMD Wait For Finger sent
> >      > Received 0x55
> >      > CMD Get Image sent
> >      > Received 18432
> >      >
> >      >
> >      > If others confirm maybe Igor can modify the driver?
> >      >
> >      > On 2018-01-17 12:12, Igor Filatov wrote:
> >      >> Looks like o1ca as well
> https://github.com/iafilatov/libfprint/pull/4
> >      >> I wonder if we can get a list of ids if devices like these.
> >      >>
> >      >> 2018-01-17 12:50 GMT+02:00 Sébastien Béchet <
> sebastien.bechet at osinix.com <mailto:sebastien.bechet at osinix.com>>:
> >      >>> Hello,
> >      >>>
> >      >>> In attachment what I understood from the documentation.
> >      >>>
> >      >>> must work for
> >      >>>
> >      >>> 0x04f3,0x0903
> >      >>> 0x04f3,0x0907
> >      >>> 0x04f3,0x0C03
> >      >>> 0x04f3,0x0C16
> >      >>>
> >      >>> Please try it.
> >      >>>
> >
> _______________________________________________
> 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/20180117/13a9fb6e/attachment.html>