3962372f47
tests: add identify test for driver goodixmoc
...
add identify ioctl file, modify custom.py add identify test
2020-09-14 09:55:55 +00:00
f67f61c638
goodixmoc: Add identify function
...
this device support verify and identify both, actually call the same
interface.
2020-09-14 09:55:55 +00:00
d5f7f4dfaa
goodixmoc: Prevent incorrect firmware type running
...
only firmware type:APP can function well, if device flash in a factory
or test firmware, report a error tips user update firmware by fwupd
2020-09-14 09:55:55 +00:00
ce6961d165
image-device: Fix cancellation documentation
...
Image devices are simply deactivated suddenly. As such, the cancellation
logic of FpDevice is not really useful there, but the documentation was
apparently accidentally copied unmodified.
2020-09-07 12:12:34 +02:00
30e1a68344
ci: Build flatpak using GNOME runner and template
2020-09-03 09:42:28 +02:00
5b087ed848
demo: Switch to use GNOME 3.36 runtime
2020-09-03 09:41:11 +02:00
5d0481b031
context: Lower severity of warning if USB fails to initialise
...
This is unlikely to happen in a real world scenario and currently breaks
running the CI test (not the umockdev based ones) while building the
flatpak. Lower the severity to avoid aborting because there is a
warning.
2020-09-03 09:41:11 +02:00
596d22a449
context: Fix invalid accesses to GUsbContext if USB is missing
...
When USB cannot be initialised (inside the flatpak build environment),
then we would have invalid accesses to the NULL pointer. Fix those.
2020-09-03 09:41:11 +02:00
c85f385191
tests: add test for goodixmoc driver
2020-09-01 16:39:06 +08:00
eb2aaaaa20
drivers: add goodix moc sensor driver support
2020-09-01 16:39:06 +08:00
e3c009c5b3
fp-device: add new type FpDeviceError FP_DEVICE_ERROR_DATA_DUPLICATE
2020-09-01 16:39:06 +08:00
a4f7293f32
synaptics: retry get version command once when receiving non-success
...
status
2020-08-21 17:42:00 +08:00
8b64312f4b
synaptics: support sensors pid 0xe9 & 0xdf
2020-07-31 09:47:35 +08:00
16c780c302
debian/changelog: Fix bug number
...
Damned copy-paste (and my vimrc...)!
2020-06-19 19:34:27 +02:00
349e30e3ae
Finalise changelog
2020-06-19 17:38:55 +02:00
13dcb8620b
Update changelog
2020-06-19 17:37:26 +02:00
70f4f2c5a4
libfprint-2-tod1.symbols: Add new TOD symbols
...
No ABI change
2020-06-19 17:37:26 +02:00
5e6ce9fe55
debian/rules: Be strictier about symbol changes
2020-06-19 17:37:26 +02:00
dc0371256f
debian/rules: Be strictier about symbol changes
2020-06-19 17:35:01 +02:00
ef37ef2004
debian/control: Add missing libfprint-2-tod-dev dependencies
...
Compiling drivers with TOD requires various libraries that we were not
properly listing.
This is based on the libfprint-2-tod-1.pc content file.
LP: #1884267
2020-06-19 17:11:19 +02:00
28bbd94ec9
git_reading_pointer.patch: Dopping
2020-06-19 16:44:18 +02:00
369e91feb4
Update upstream source from tag 'upstream/1.90.2+tod1'
...
Update to upstream version '1.90.2+tod1'
with Debian dir 65dc429037
2020-06-19 16:43:04 +02:00
1d94579d84
New upstream version 1.90.2+tod1
2020-06-19 16:42:56 +02:00
0e123d0752
Merge tag 'v1.90.2' into tod
...
Tag 1.90.2
2020-06-19 16:27:51 +02:00
7c359b9135
Update changelog
2020-06-19 16:17:54 +02:00
7b9a8e0dfb
git_reading_pointer.patch: Dopping
2020-06-19 16:17:54 +02:00
2ba95f2ad5
Update upstream source from tag 'upstream/1.90.2'
...
Update to upstream version '1.90.2'
with Debian dir b87656b655
2020-06-19 15:48:35 +02:00
748bfa09ce
New upstream version 1.90.2
2020-06-19 15:48:26 +02:00
b7e27bfdc6
demo: Handle the non-imaging mode also if we get a non-supported error
...
Image devices may return a FP_DEVICE_ERROR_NOT_SUPPORTED error once capture
is already started, in such case handle the error going in non imaging mode
2020-06-17 14:16:34 +02:00
37b19674f1
verify: Use fast matching callback also for non-storage devices
2020-06-17 14:14:50 +02:00
a5f4ad507a
img-capture: Exit with error if the device doesn't support capture
2020-06-17 14:12:43 +02:00
1f96077e36
examples: Don't try to save an image from a print without it
...
A device may produce both prints with image data and not, so only do it
in the case the prints contains image data
2020-06-17 14:00:19 +02:00
ed26976ac5
fpi-usb-transfer: Use the same values of libusb for transfer types
2020-06-16 22:50:47 +02:00
e4d292b595
fp-image-device: Properly include fp-device.h
2020-06-16 22:49:38 +02:00
c6b8430c72
fpi-print: Improve debug on print score
2020-06-16 22:49:18 +02:00
cbf1dcca29
fpi-image-device: Improve debugging messages
2020-06-16 22:48:51 +02:00
7f7d099ba0
fpi-device: Don't double check for cancellable value
...
g_cancellable_is_cancelled already handles properly null values
2020-06-16 22:43:18 +02:00
b6f965c1d9
fpi-device: Use the current action string instead of value
2020-06-16 22:42:34 +02:00
fd2875aa3e
examples: add img-capture example
...
This one can be useful in scripts, e.g. for building fingerprint
dataset.
2020-06-13 09:20:28 -07:00
bb4844012b
Import Debian changes 1:1.90.1+tod1-0ubuntu4
...
libfprint (1:1.90.1+tod1-0ubuntu4) focal; urgency=medium
* Rebuild with the new libgusb
libfprint (1:1.90.1+tod1-0ubuntu3) focal; urgency=medium
* Rebuild with the current libgusb (lp: #1867639 )
2020-06-11 20:51:00 +02:00
4b2816db64
Update for 1.90.2
2020-06-08 11:40:02 +02:00
4af3e59174
uru4000: Always detect whether encryption is in use
...
This is based on the patch and observation from Bastien that some
URU4000B devices do not use encryption by default (it is a configuration
stored within the firmware). As such, it makes sense to always detect
whether encryption is in use by inspecting the image.
The encryption option would disable flipping of the image for the
URU400B device. Retain this behaviour for backward compatibility.
2020-06-05 15:53:53 +00:00
24b1faffde
upeksonly: Add a comment that multiple URBs are needed
2020-06-05 17:44:36 +02:00
49983c8ee7
upeksonly: Fix memory leak of register data helper struct
2020-06-05 17:44:36 +02:00
d276c3489e
upeksonly: Fix register write value
...
The value was set after the transfer was submitting, causing the value
to always be zero.
2020-06-05 17:44:36 +02:00
3f51e6dcb6
upeksonly: Pass required user data to write_regs_cb
...
The user data for write_regs_cb needs to be set to wrdata. This was
simply missing, add the appropriate argument.
2020-06-05 17:44:36 +02:00
b4dbbd667a
upeksonly: Avoid reading beyond received packet boundary
...
The code would just read 4096 bytes from the packet, without checking
the size and neither setting short_is_error. It is not clear whether
packets from the device are always 4096 bytes or not. But the code
assume we always get a full line, so enforce that and use the actual
packet size otherwise.
2020-06-05 17:44:36 +02:00
7d9245505f
upeksonly: Remove callback support after killing transfers
...
This seems to have been unused even before the v2 port.
2020-06-05 17:44:36 +02:00
570daf2321
upeksonly: Remove ABORT_SSM constant
...
This was not used. The old driver used this if creating a USB transfer
failed, however, we delay any such failures (which cannot really happen)
into the callback today, where the error is handled differently.
2020-06-05 15:40:17 +00:00
60d0f84294
upeksonly: Fix creation of image transfers
...
The GPtrArray needs to be created at some point. Also, reference
counting was wrong as submitting the transfer sinks the ref, but we rely
on it surviving.
Note that we really should change this to only have one in-flight
transfer and starting a new one after it finishes.
Co-authored-by: Vasily Khoruzhick <anarsoul@gmail.com >
2020-06-05 15:40:17 +00:00
boger.wang