Any news on this? Was Daniel able to take a look at the snoop captures? Regards
On 2/20/08, Axel Mammes <[EMAIL PROTECTED]> wrote: > > I downloaded the latest git version and I patched the AES4000 driver's USB > VID&PID to match my device. > > Here is stdout: > [EMAIL PROTECTED] ~]# strace -o /root/straceFprintDemo.log fprint_demo > > fprint_demo_stdout.log > fp:debug [fp_init] > fp:debug [register_driver] registered driver upekts > fp:debug [register_driver] registered driver uru4000 > fp:debug [register_driver] registered driver aes1610 > fp:debug [register_driver] registered driver aes2501 > fp:debug [register_driver] registered driver aes4000 > fp:debug [register_driver] registered driver upektc > fp:debug [register_driver] registered driver fdu2000 > fp:debug [find_supporting_driver] driver aes4000 supports USB device > 08ff:afe4 > fp:debug [fp_dev_open] > fp:debug [fp_enroll_finger_img] aes4000 will handle enroll stage 0/0 > (initial) > fp:debug [fpi_imgdev_capture] aes4000 will handle capture request > aeslib:debug [aes_write_regv] write 56 regs > aeslib:error [do_write_regv] bulk write error -2 > fp:error [fpi_imgdev_capture] capture failed with error -2 > fp:error [fp_enroll_finger_img] enroll failed with code -2 > > I am attaching an strace too. Thanks to dave007 and dererkazo for the help > on freenode. > > Regards > Axel >
_______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
