Re: [fprint] Driver for Upek Eikon model no. TCRD4C4 (aka. Eikon II)
Here's an updated patch. In this patch, instead of replacing the upekts driver, I created a new driver called upek2e. The driver is not compiled by default, because of the problems with the upeksonly driver sharing IDs with this driver. To compile this driver, you must include it in the --with-drivers option when configurying: By example: ./configure --with-drivers=upek2e upekts Why a new driver? * The verification is exactly the same as the upekts one. Copy-paste. * There are some changes in the enrollment, and surely more changes will follow since this was only tried on two device variants (and there are still some issues on both of them). * The initialization part is almost completely different. With this driver, I want to create a sandbox to test better the targeting devices, without messing up with the original upekts driver. Since we're maintaining the same code structure as the upekts driver, when this code becomes more tested and solid we'll be able to incorporate back the changes in a future --if we still think that is a good idea at that time. Link: http://sharing.jorgesuarezdelis.name/2010/libfprint-0.1.0~pre2 +upeke2driver.diff Hope you like the idea. Comments will be very welcomed, of course :) -- Jorge Suárez de Lis y...@jorgesuarezdelis.name ___ fprint mailing list fprint@reactivated.net http://lists.reactivated.net/mailman/listinfo/fprint
Re: [fprint] [Fwd: Re: Upek Eikon II]
The upeksonly device seems to work *very* differently to the other two devices. The upeksonly driver has not the same structure as the upekts driver as well, and we should need to take a very deep look into its code to do the matching. I mean, that would be a lot of hard work. I like your idea, because that would fix the ids issue. But that's too much work and I'm not very confident that merging two drivers that seem so different would be the best solution. Comments about this would be very appreciated. I actually don't want to do this if we are able to find a smarter solution. -- Jorge Suárez de Lis y...@jorgesuarezdelis.name ___ fprint mailing list fprint@reactivated.net http://lists.reactivated.net/mailman/listinfo/fprint
Re: [fprint] Driver for Upek Eikon model no. TCRD4C4 (aka. Eikon II)
Sorry by the confussion. The driver is called upek2e. The configure example should be: ./configure --with-drivers=upeke2 upekts -- Jorge Suárez de Lis y...@jorgesuarezdelis.name ___ fprint mailing list fprint@reactivated.net http://lists.reactivated.net/mailman/listinfo/fprint
[fprint] Usb snoop help
Hello, I'm trying to add support to Upek Eikon (model no. TCRD4CA1H6A3), whose ID is 147e:2016. It has the same device id that the one supported by the driver upeksonly, but I think this is like the upekts one, 0483:2016. I'm trying to sniff the USB data from the official privative driver available at http://www.upek.com/support/downloads/linux/ to try to adapt the driver. However, I'm stuck. I need to capture very long data streams and usbmon debugfs interface won't let me see more than 32 bytes The usbmon.txt from the kernel documentation says: The length of collected data is limited and can be less than the data length report in Data Length word. The output is like this (The data should have 112 bytes, but I only can see 32): 880099005180 3714163885 S Bo:3:002:2 -115 112 = 4369616f 00306728 6400 0803 0100 3100 3800 How can I see the full data? Is this a limitation of usbmon? How could I sniff all the data? Thank you. -- Jorge Suárez de Lis ___ fprint mailing list fprint@reactivated.net http://lists.reactivated.net/mailman/listinfo/fprint
