| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
New values taken from a newer version of the official driver.
|
|
* Allow FPI_PRINT_NBIS to be extended rather than overridden if a user
supplies an existing FpPrint template with data;
* Prints will only be extended if a device has the required feature.
For image-based devices this feature is added by default since they
typically do not have storage (this can be overridden at the child
class level).
Extending an existing FpPrint requires passing a template print with
existing data during the enrollment process. This is done because the
caller is responsible for maintaining the fingerprint database and doing
the necessary deserialization operations if needed. The existing
example program is updated to show how to do that.
|
|
|
|
Otherwise tightly looping SSMs (primarily SPI transfers), will flood the
logs in inappropriate ways.
|
|
Two of the printed variables were only calculated after the message was
printed, making the logged information less useful than it could be.
|
|
This ensures that we have processed all hotplug events before
considering enumeration to be complete. This is important due to USB
persist being turned off. At resume time, devices will disappear and
immediately re-appear. In this situatoin, enumerate could first see the
old state with a removed device resulting in it to not be discovered.
As a hotplug event is semingly emitted by the kernel immediately, we
can simply make sure to process this hotplug event before returning
from enumerate.
Closes: fprintd#119
|
|
Added description and fixed incorrect name in comment, so now gtkdoc
actually shows useful information.
|
|
|
|
|
|
|
|
|
|
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
|
|
This as per the same reasons of commit 63bfaf4, and without trailing new
lines such attributes aren't picked by umockdev in ubuntu and debian.
|
|
63CC: Dell Latitude series fingerprint sensor
|
|
Signed-off-by: hermanlin <herman.lin@emc.com.tw>
|
|
|
|
|
|
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
|
|
This is needed for the fprintd duplicate checking code. The information
is needed to delete stale prints automatically from the device.
Related: #415
|
|
This allows creating tests both for image and non-image devices using
the same script.
|
|
63BC: Dell XPS series fingerprint sensor
|
|
|
|
See https://github.com/systemd/systemd/pull/20756
|
|
|
|
Otherwise forks will not find the image and things fall apart (due to
the method of how we build the image).
|
|
It is needed by tests/test-generated-hwdb.sh and is not pulled in
indirectly anymore.
|
|
|
|
Really, it shouldn't matter, as there is no return. But adding the NULL
initializer does not harm either.
|
|
This fixes the flatpak build.
|
|
And update instructions for the simpler method.
Co-authored-by: Benjamin Berg <bberg@redhat.com>
|
|
This is inelegant, but allows API consumers to match the FpDevice with
an OS device.
|
|
|
|
This test requires control transfer replay fixes that will be contained
in umockdev 0.16.3. Bump the requirement accordingly.
Closes: #412
|
|
It appears the kernel automatically "fixes" this mistake and it works.
the transfer in question is an interrupt transfer and should be submitted
as such. Do that in order to make things more correct and so that the
test can run.
|
|
This capture was made using a "COBO" branded device, and uses the new
pcapng format.
|
|
|
|
|
|
This reverts commit 8f93aef1221eb1b2dfc81c5dbacede8a07b86118.
|
|
This reverts commit 0dcb4be4d30197b02a6fddba34ce6f7b393cec6c.
|
|
And update instructions for the simpler method.
|
|
This is inelegant, but allows API consumers to match the FpDevice with
an OS device.
|
|
|
|
It should be included in files requiring it only.
|
|
|
|
|
|
|
|
|
|
|
|
This matches the expectation. i.e. we return no-match and we do not
return a scanned print as we don't have anything for it. If we did
indeed return a scanned print, then fprintd would try to delete it
during enroll and would then fail.
Note that we do *not* return a DATA_NOT_FOUND error in the storage
device if the print does not exist. This is because not all devices
support reporting this error. It is therefore more sensible to handle it
gracefully and expect test setups to set the error explicitly for
testing purposes.
|
