lp:libfprint

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

1294. By Marco Trevisan (Treviño) on 2021-04-12

libfprint2-sections: Add missing FpFingerStatusFlags

1293. By Marco Trevisan (Treviño) on 2021-04-12

ci: Expose coverage report and meson logs in MRs

1292. By Marco Trevisan (Treviño) on 2021-04-12

device: Deprecate fp_device_{supports,has}_* functions for has_feature

We can avoid having multiple device feature-check functions now and
just rely on a few.

Add uncrustify config to properly handle begin/end deprecation macros.

1291. By Marco Trevisan (Treviño) on 2021-04-12

device: Expose supported features publicly as FpDeviceFeature

It can be convenient for device users to check what it supports, without
having multiple functions to check each single feature.

So expose this and add tests.

1290. By Marco Trevisan (Treviño) on 2021-04-12

fp-device: Gracefully handle capture calls on devices with no support

1289. By Marco Trevisan (Treviño) on 2021-04-12

device: Make verification support optional

We always assumed a device can verify, but nothing prevents from having
a device that only can identify or capture.

So, given that we've more fine grained checks, let's stop the task if
this is the case.

1288. By Marco Trevisan (Treviño) on 2021-04-12

fpi-device: Add FpiDeviceFeature flags to FpDeviceClass

Allows drivers to define more fine grained features for devices, not
strictly depending on assumptions we can make depending on the
implemented vfuncs.

We keep this per class but could be in theory moved to each instance.

In any case, added an utility function to initialize it in the way we
can ensure that we've a consistent way for setting them across all the
devices.

1287. By Huan Wang <email address hidden> on 2021-04-12

Add nb1010 driver

1286. By Matthew Mirvish on 2021-04-11

upeksonly: fix double free in usb transfer cbs

Some USB transfer callbacks in this driver were freeing their transfer
buffer in their callbacks, which causes a double free since the transfer
itself frees them afterwards. Probably just got missed during the V2 api
changes.

1285. By Benjamin Berg <email address hidden> on 2021-04-08

spi-transfer: Add SPI transfer helper routines

These routines assume that any messages is composed of a write and/or
read part. While the API allows sending and receiving as part of one
messages/transfer, it does not permit full duplex operation where data is
both send and received at the same time.