Synaptics Fingerprint Driver quickstart

Quickstart

• Current project direction — Jira problems/features/tasks, Git solutions and Actions evidence.
• Driver–firmware integration — external firmware ownership and driver-owned command/update contracts.
• GitHub Actions evidence — what each run proves and what it does not.

What this project is

The project delivers a customer-configured Windows fingerprint driver. Windows WBF requests enter the wrapper/driver, flow through niseCore’s VFM, sensor, matcher and storage layers, cross firmware command contracts from biometrics-include, and are built/released from the customer matrix. utest supplies focused source-derived tests and virtual specifications.

flowchart LR
  Windows[Windows Biometric Framework] --> Adapter[Sensor / Engine / Storage adapters]
  Adapter --> Device[CBiometricDriver + CBiometricDevice]
  Device --> Capture[CaptureImage + worker threads]
  Device --> Power[Power, wake, pairing and side-channel control]
  Capture --> Bridge[vfmCoreEntry]
  Power --> Bridge
  Adapter --> Bridge
  Bridge --> Core[niseCore VFM API]
  Device --> Bus[USB / SPI / HID device classes]
  Bus --> Sensor[Fingerprint sensor]
  Customer[CustomerProjects props] -. configures .-> Adapter
  Customer -. configures .-> Device
  Services[Policy / reset / monitor / CTAP services] --> Device
  Package[Driver and service packages] -. delivers .-> Device

Configured evidence snapshot

Repository	Responsibility	Configured branches
niseCore	Core biometric runtime and driver library	hisd/customer/6_01_mainbranch_20260506, hisd/customer/Dell_MisPowerButton_Triton_20251205, hisd/customer/hp_cmit_mis_20251203, hisd/release/6_00_mainbranch_20251127, wip/vincenth/rust_dev_20260506
WBF wrapper	Windows Biometric Framework adapter, UMDF/WDF driver and customer package	hisd/customer/6_01_mainbranch_20260506, hisd/customer/Dell_MisPowerButton_Triton_20251205, hisd/customer/hp_cmit_mis_20251203, hisd/release/lenovopbautility_20181116, wip/vincenth/rust_dev_20260506
Driver build and release	Customer matrix and delivery orchestration	master
Unified tests	Source-derived unit, virtual and WBF workflow tests	dev, main
Biometrics include	Shared firmware command and hardware identity contracts	master

Task routing

Intent	Read first	Primary source	Validation
Understand an end-to-end fingerprint operation	Cross-repo workflows	WBF CBiometricDevice and niseCore VFM APIs	Relevant utest WBF/niseCore suite
Change sensor, matcher or template behavior	niseCore architecture	niseCore sensor/, matcher/, storage/, vfmCore/	niseCore focused GTest plus customer build
Change Windows capture/power behavior	WBF component interactions	wbdi/driver/BiometricDevice.*, adapters	WBF capture/wake utests and driver package build
Change a firmware command/update path	Firmware integration	WBF update/command + niseCore sensor + vcsfw_*.h	Host tests plus joint driver/firmware compatibility evidence
Add or update a customer	Customer variants	.github/customers.json and WBF CustomerProjects/	Matrix build for that exact refs/project/target
Change delivery automation	Deployment	driver-build workflows/actions	Manual filtered release then matrix reconciliation
Add a unit/virtual test	Testing	utest dev pipeline/spec/CMake	Extract → build → run with target ref/variant

Rules of interpretation

• Requirement means approved intent only when backed by an approved source. Current baseline requirements are candidates inferred from implementation and delivery configuration.
• Implementation is what the frozen source revision does.
• Branch difference is based on tree/diff evidence; product impact is separately labeled inference.
• Test evidence proves only the executed checks. A missing or skipped run is not success.