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