>> I don't think there's any way to do this on fprint. I still have to take >> a better look at the code, but it seems that the drivers just register >> themselves as "I am ready to support the device with these IDs, so I'll >> do the job".
I have an upeksonly device. It must be possible to differentiate the devices at runtime and merge the drivers so that while using one driver, different code paths are followed. Ive posted several patches to this list that for while made my upeksonly work quite decently but after some kernel update something in the data transfer broke. Swiping fast enough to get a print before a gap was detected became a chore. I if you want to merge the only driver to upekts, I can provide testing and diagnostics. -- --Alexia _______________________________________________ fprint mailing list fprint@reactivated.net http://lists.reactivated.net/mailman/listinfo/fprint
