On Nov 17, 2007 9:03 PM, Vishal Rao <[EMAIL PROTECTED]> wrote: > In the mean time let me try to find time this weekend to try adding > the usb id to the AES2501 driver and see if that works!
No go. Just simply replacing the usb id in aes2501.c for the aes1610 did not work (duh). The fprint_demo shows a status "could not open device", using the unmodified aes2501.c and the demo does not find any devices, of course. Hacking the code to get it to work is beyond me, but since I have an aes1610 device I can test any code (from the debian mailing list) you have for the device, if you need me to... -- "Thou shalt not follow the null pointer for at it's end madness and chaos lie." _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
