[fprint] U.are.U 4000 Reader

Sébastien Morin smsisko at gmail.com
Sat Dec 1 14:47:18 GMT 2007


On Dec 1, 2007 9:19 AM, Daniel Drake <dan at reactivated.net> wrote:

>
> What about img_capture_continuous? That one has no finger-on-sensor
> detection.
>
>
Here is the output from the log, and the image stays blank:

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 [find_supporting_driver] driver uru4000 supports USB device
05ba:0007
Found device claimed by Digital Persona U.are.U 4000/4000B driver
uru4000:debug [get_hwstat] val=85
uru4000:debug [do_init] rebooting device power
uru4000:debug [set_hwstat] val=05
uru4000:debug [get_hwstat] val=00
uru4000:debug [get_hwstat] val=05
uru4000:debug [set_hwstat] val=85
uru4000:debug [fix_firmware] encryption byte at 793 reads 07
uru4000:debug [set_hwstat] val=05
uru4000:debug [get_hwstat] val=00
uru4000:debug [get_irq_with_type] type=56aa
uru4000:debug [get_irq] irq type 56aa
fp:debug [fp_dev_open]
using Xv format 0x32595559 YUY2 packed
using Xv format 0x32595559 YUY2 packed
Press S to toggle standardized mode, Q to quit
fp:debug [fpi_imgdev_capture] uru4000 will handle capture request
uru4000:debug [set_mode] 20
fp:debug [fpi_img_new] length=111424

However if I try with the 4000B I get the image for each frame...

As far as I can tell the debug output is basically the same for either
devices.

-- 
Sébastien Morin
smsisko at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.reactivated.net/pipermail/fprint/attachments/20071201/330a3444/attachment.html


More information about the fprint mailing list