Whet were the changes made so that AES1610 could be recognized? Asking this as my laptop has a AES1610 and if the lib is not loaded, then it's no use for me.
Thanks, Miguel Quoting Daniel Drake <[EMAIL PROTECTED]>: > Michele B. wrote: >> Hello to all, >> >> First of all thanks for your efforts in developing all this! >> I just wanted to ask you if you didnt interface the aes1610 driver on >> purpose in this release of libfprint or not. >> I use a Samsung X65 notebook with the AuthenTec Reader and found out >> libfprint doesnt recognize it because the driver is not loaded. > > Oops, that was an oversight, thanks for pointing it out. I don't have > this hardware to test with, so it slipped through the gap. > Apparently we haven't spread the word to enough AES1610 users yet... :) > >> I just added the corresponding lines to fp_internal.h and core.c >> (simply look at the uru4000 drivers and others) that were missing and >> now it works more or less. Just some strange error about >> >> fp:error [fpi_imgdev_capture] no image height assigned >> >> but I guess it´s normal. > > That's a bug in the current code where the scan was not good enough but > the driver didn't report that, it instead returns an invalid image. In > other words, your scanning technique was bad -- you didn't scan for long > enough or something like that. > >> P.S. Can u tell me a best practice to scan my finger? I couldnt manage >> to make it verify even once for now. > > Use fp_demo as it provides visual information on your scan, and get a > good enrollment image. > > Thanks, > Daniel > _______________________________________________ > fprint mailing list > [email protected] > http://lists.reactivated.net/mailman/listinfo/fprint > _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
