| name | libfprint-patch-build |
| description | Use when adapting the EH575 work into an EH577 libfprint driver, editing the local WIP driver files, comparing against upstream libfprint Egis drivers, or building libfprint to validate the EH577 port. |
Patch And Build Libfprint
Use this when the task is in the driver porting path rather than the live probe path.
Read first
Read only what is needed for the current edit:
AGENTS.md
wip-libfprint/drivers/egis0577.c
wip-libfprint/drivers/egis0577.h
refs/EgisTec-EH575/libfprint.patch
refs/libfprint/libfprint/drivers/egis0570.c
refs/libfprint/libfprint/drivers/egismoc/egismoc.c
Porting stance
Default assumptions:
- EH577 should be treated as EH575-family hardware
- start from the EH575 patch structure, not from scratch
- keep response handling flexible where state bytes have already varied
- do not model EH577 as
egismoc unless new endpoint or packet evidence forces that
Preferred edit order
- Update device IDs and driver registration.
- Keep sequence tables aligned with the known-good EH575 replay path.
- Relax reply parsing where state bytes are known to vary.
- Preserve room for later interrupt integration instead of assuming interrupts are unused.
- Validate the edited driver against captured logs and dumps before broad refactors.
Build and Testing Workflow
The upstream reference tree is under refs/libfprint/ and uses Meson.
1. Local Build & CLI Testing (Development)
For rapid development, avoid installing to the system. Build locally and test using the provided helper script which injects :