- 03 Nov, 2021 10 commits
-
-
Marco Trevisan authored
-
Marco Trevisan authored
-
Marco Trevisan authored
-
Marco Trevisan authored
-
Marco Trevisan authored
These are not fatal for package installation and rebuild postinst script
-
Marco Trevisan authored
-
Marco Trevisan authored
-
Marco Trevisan authored
-
Marco Trevisan authored
Update to upstream version '1.94.2' with Debian dir ccbb696b9be409b1f86302618c78cc99039153f2
-
Marco Trevisan authored
-
- 02 Nov, 2021 2 commits
-
-
Benjamin Berg authored
-
Benjamin Berg authored
-
- 28 Oct, 2021 2 commits
-
-
Marco Trevisan authored
-
Marco Trevisan authored
-
- 27 Oct, 2021 7 commits
-
-
Marco Trevisan authored
-
Benjamin Berg authored
The length is only a single byte in the transfer. However, the struct had a uint32_t in that place, breaking the sizeof() calculation and seemingly creating issues for certain lengths of user id strings (which depend on the username). Fix this by changing the type to uint8_t. Also add the initial 0x43 prefix byte and a byte of apparent padding that the struct contains. Leave the two reserved bytes at the end, as they seem to actually have a meaning (i.e. they are seemingly send in listings). This effectively makes the struct one byte smaller, bringing it down to 127 bytes from 128 bytes. Closes: #428, #404
-
Marco Trevisan authored
-
Marco Trevisan authored
-
Marco Trevisan authored
-
Marco Trevisan authored
This is needed for SPI devices
-
Marco Trevisan authored
This as per the same reasons of commit 63bfaf4f, and without trailing new lines such attributes aren't picked by umockdev in ubuntu and debian.
-
- 26 Oct, 2021 9 commits
-
-
Marco Trevisan authored
-
Marco Trevisan authored
-
Marco Trevisan authored
LP: #1945296
-
Marco Trevisan authored
-
Marco Trevisan authored
-
Marco Trevisan authored
-
Marco Trevisan authored
Update to upstream version '1.94.1' with Debian dir e02e11ad9d3bc0154d4df35b7cea33c44f37385a
-
Marco Trevisan authored
-
Marco Trevisan authored
It was set to a testing location for development purposes, and it got wrongly committed.
-
- 20 Oct, 2021 1 commit
-
-
boger authored
63CC: Dell Latitude series fingerprint sensor
-
- 12 Oct, 2021 1 commit
-
-
hermanlin authored
Signed-off-by:hermanlin <herman.lin@emc.com.tw>
-
- 24 Sep, 2021 3 commits
-
-
Benjamin Berg authored
-
Benjamin Berg authored
-
Benjamin Berg authored
While useful, there are advantages for this to be done by the surrounding code (i.e. fprintd). As such, remove the identify stage from the goodix driver and rely on fprintd doing it for us. One can probably argue that neither solution is perfect. Ideally, we would probably return the information required to delete the old print to the upper stack and let the driver/device handle the duplicate checking. However, for now this works well. We may need to reconsider this if we get devices that do the duplicate checking transparently and just throw an enroll error. NOTE: The driver did not report any progress for the identify step. As such, the number of enroll steps reported by the device remain the same. Closes: #415
-
- 21 Sep, 2021 2 commits
-
-
Benjamin Berg authored
This is needed for the fprintd duplicate checking code. The information is needed to delete stale prints automatically from the device. Related: #415
-
Benjamin Berg authored
This allows creating tests both for image and non-image devices using the same script.
-
- 17 Sep, 2021 3 commits
-
-
boger authored
63BC: Dell XPS series fingerprint sensor
-
Benjamin Berg authored
-
-