Re: [fprint] Planning libfprint API changes (2.x)

2019-08-13 Thread Benjamin Berg
Hi, that is useful in general. For now I am focused on ensuring that already working devices keep working though; i.e. fixing non-functional devices is not a priority for me currently. Could you maybe check that there is a bug open on https://gitlab.freedesktop.org/libfprint/libfprint/issues w

Re: [fprint] Planning libfprint API changes (2.x)

2019-08-13 Thread Md Mozammel Hossain
Hello, I do have a Xiaomi laptop which use Elantech device, currently its not working even though it on supported device list. I can help to test new driver. *--Best Regards,* *Mozammel Hossain* *M: +95 9786256424* On Mon, Aug 12, 2019 at 7:28 PM Benjamin Berg wrote: > Hi, > > I am wrappin

Re: [fprint] Planning libfprint API changes (2.x)

2019-08-12 Thread Benjamin Berg
Hi, I am wrapping up the libfprint update, and I am also adding automated tests using umockdev. In the future, it will be mandatory for drivers to ship a simple umockdev based test case. This is something where I would really appreciate help. If anyone has a device, please have a look at the test

Re: [fprint] Planning libfprint API changes (2.x)

2019-07-10 Thread Benjamin Berg
Hi, On Wed, 2019-07-10 at 19:39 +0200, Peter Maatman wrote: > I've just tested the etes603 driver. Thanks! > There seem to be some issues > with the cancelling which I'll investigate further this weekend. > Seems to have to do with not closing the device properly after > the cancellation, after

Re: [fprint] Planning libfprint API changes (2.x)

2019-07-10 Thread Peter Maatman
Hey, I've just tested the etes603 driver. There seem to be some issues with the cancelling which I'll investigate further this weekend. Seems to have to do with not closing the device properly after the cancellation, after which the gtk test program segfaults when you try to start a new capture.

Re: [fprint] Planning libfprint API changes (2.x)

2019-07-10 Thread Benjamin Berg
Hey, On Wed, 2019-07-10 at 14:21 +0200, Bastien Nocera wrote: > > … Most drivers have been ported at this point (fixing a > > number of issues in the process). > > Anything that could be backported? Failing that, an issue filed per > problem would go a long way towards cleanups for 1.0. There we

Re: [fprint] Planning libfprint API changes (2.x)

2019-07-10 Thread Bastien Nocera
On Wed, 2019-07-10 at 14:09 +0200, Benjamin Berg wrote: > Hi everyone, > > so, I have worked on this for a while now, and I pushed my changes to > the > > https://gitlab.freedesktop.org/libfprint/libfprint/commits/wip/benzea/v2 > branch. > > This is not yet quite complete. Some changes are mor

Re: [fprint] Planning libfprint API changes (2.x)

2019-07-10 Thread Benjamin Berg
Hi everyone, so, I have worked on this for a while now, and I pushed my changes to the https://gitlab.freedesktop.org/libfprint/libfprint/commits/wip/benzea/v2 branch. This is not yet quite complete. Some changes are more invasive, others are less so. Most drivers have been ported at this point

[fprint] Planning libfprint API changes (2.x)

2019-06-18 Thread Benjamin Berg
Hi, I realised that I only had talked to a few individuals about this, so it seems like a good idea to inform the ML about some of the ideas. The current situation is that we are looking at adding support for devices that store the print data in the sensor. With these devices, a few new operation