1. 08 Nov, 2020 1 commit
    • Marco Trevisan's avatar
      verify/enroll: Save and use locally saved prints also for devices with storage · 3b993fab
      Marco Trevisan authored
      Some devices have storage but that's is limited enough not to be able
      to store all the metadata, but just a fingerprint id.
      
      In such case we also need to use the local storage to be able to verify.
      Fprintd does this already, but we don't do it in the libfprint examples.
      
      So, in in case we enroll, always save the print information to the disk,
      while in case we verify we try to load the print from disk and we use
      that in case its private data matches the one provided by the device.
      3b993fab
  2. 07 Nov, 2020 4 commits
  3. 05 Nov, 2020 2 commits
    • Benjamin Berg's avatar
      tests: Add a new test for vfs301 · ae3baadc
      Benjamin Berg authored
      See: #320
      ae3baadc
    • Benjamin Berg's avatar
      tests: Store temporary directory on failure · 4f29a32d
      Benjamin Berg authored
      It is not very useful to just delete the data again after a failure, as
      it might be useful for debugging. Just store it into an "errors"
      subdirectory of the PWD in the hope that this is a sane location.
      
      Note that it'll error out if the directory already exists, but that
      should be acceptable in all cases. i.e. it won't exist in the CI and
      developers can just wipe the directory.
      4f29a32d
  4. 04 Nov, 2020 5 commits
    • Benjamin Berg's avatar
      vfs301: Start capture only on state change to AWAIT_FINGER_ON · e5fa54e8
      Benjamin Berg authored
      Start the capture when the state changes to AWAIT_FINGER_ON instead of
      assuming that the device should always be active.
      
      Closes: #320
      e5fa54e8
    • Benjamin Berg's avatar
      vfs301: Fix device pointer handling in callback · d3076039
      Benjamin Berg authored
      When porting the driver to the new libfprint 1.90.0 a mistake was made
      where the device was not passed through user_data anymore but it was
      still read from there. Stop using user_data in the callback to fix this.
      
      See: #320
      d3076039
    • Benjamin Berg's avatar
      elan: Simplify elan driver internal state machine · a748f4d3
      Benjamin Berg authored
      The elan driver always "deactivates" the device after a cpature run. We
      can simplify the while internal state into a single "active" state and
      rely on the image device driving this state machine correctly.
      
      i.e.:
       * We start a callibrate/capture/deactivate when we go into the
         AWAIT_FINGER_ON state
       * We only store the fact that we are active and want to deactivate
       * We rely on the image device never going into the AWAIT_FINGER_ON
         state without first waiting for the finger to be off (which implies
         deactivation).
      a748f4d3
    • Benjamin Berg's avatar
      image-device: Redefine internal states and valid transitions · 3ee5536a
      Benjamin Berg authored
      This adds a number of new internal states to better capture what is
      going on. Also added are checks that all transitions we make are in the
      set of expected and valid transitions.
      
      Only three drivers use the state_change notification. These drivers are
      updated accordingly.
      3ee5536a
    • Benjamin Berg's avatar
      image-device: Remove cancelling boolean from private data · f56aacc7
      Benjamin Berg authored
      The boolean is just used to emit a warning for unexpected state
      transitions. It is sufficient to pass it to the deactivate function
      directly for that purpose.
      f56aacc7
  5. 19 Oct, 2020 4 commits
  6. 15 Oct, 2020 1 commit
  7. 14 Oct, 2020 2 commits
  8. 07 Oct, 2020 7 commits
  9. 30 Sep, 2020 1 commit
    • Benjamin Berg's avatar
      usb-transfer: Work around libgusb cancellation issue · c7cab77f
      Benjamin Berg authored
      We have plenty of code paths where a transfer may be cancelled before it
      is submitted. Unfortunately, libgusb up to and including version 0.3.6
      are not handling that case correctly (due to libusb ignoring
      cancellation on transfers that are not yet submitted).
      
      Work around this, but do so in a somewhat lazy fashion that is not
      entirely race free.
      
      Closes: #306
      c7cab77f
  10. 29 Sep, 2020 4 commits
  11. 28 Sep, 2020 1 commit
  12. 14 Sep, 2020 6 commits
  13. 07 Sep, 2020 1 commit
    • Benjamin Berg's avatar
      image-device: Fix cancellation documentation · ce6961d1
      Benjamin Berg authored
      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.
      ce6961d1
  14. 03 Sep, 2020 1 commit