Luiz Angelo Daros de Luca | 4 Jul 03:36 2011
Picon

Re: RFC: [PATCH] BSAPI bridge driver for libfprint

Hello Chow,

I don't know about the others but I'm really looking for something
like these. This could also allow some benchmark test between both.
Also, this could help on reverse engeneering what is different from
other drivers on your device.

libfprint upek driver, in my case, is still unusable because of its
poor matching results.

Thanks and I really hope success for you.

I have a 147e:1000 and I will try to test your patch.

Regards,

---
     Luiz Angelo Daros de Luca, Me.
            luizluca <at> gmail.com

2011/6/29 Chow Loong Jin <hyperair <at> ubuntu.com>:
> Hi all,
>
> Seeing as there are a number of UPEK devices that weren't supported by
> libfprint, I wrote a "bsapi" driver that uses dlopen to load libbsapi.so from
> the proprietary UPEK SDK if it is present, allowing libfprint-using applications
> to access unsupported UPEK devices.
>
> I have only been able to test this with the 147e:1002 sensor that is embedded in
> my Thinkpad Edge E220S, but based on the UPEK SDK documentation, as well as
(Continue reading)

Luiz Angelo Daros de Luca | 4 Jul 04:47 2011
Picon

Re: RFC: [PATCH] BSAPI bridge driver for libfprint

Hello Chow,

I can confirm that this also works with my device. Probably, it will
work with any supported BSAPI devices.

I am not a fprint commiter and not a fprint master but I have some suggestions.

It should exists a way to switch from/to libfprint native driver
to/from bsapi one. Maybe a env variable? Have the case of multiple
drivers implementing the same device ever happened in fprint? Also, I
think that native upek*.c drivers should have precedence over bsapi
(if not set explicitily by env or compile flag).

The configure script may need some fix like checking for bsapi and
disabling the driver if libs are missing. Configure also does not list
the new driver in the drivers feedback (--with-drivers).

--- libfprint/drivers/bsapi.c.old       2011-07-03 22:54:26.000000000 -0300
+++ libfprint/drivers/bsapi.c   2011-07-03 22:54:50.000000000 -0300
 <at>  <at>  -538,6 +538,7  <at>  <at> 

 /* TODO: Complete listing of usb devices here */
 static const struct usb_id id_table[] = {
+    { .vendor = 0x147e, .product = 0x1000 },
     { .vendor = 0x147e, .product = 0x1002 },
     { 0, 0, 0, },
 };

About this usb_id list, maybe fprint workflow could be adapted to not
use id_table outside the driver. Like, instead of calling discovery
(Continue reading)

Brent Oster | 4 Jul 19:06 2011
Picon

cannot download

Hi there, I'm interested in trying out fprint.  However, when I try to
download any of the source packages at
http://people.freedesktop.org/~hadess/ I get the error: could not be
saved, because the source file could not be read.

 - Brent
Bastien Nocera | 4 Jul 19:20 2011
Picon

Re: cannot download

On Mon, 2011-07-04 at 13:06 -0400, Brent Oster wrote:
> Hi there, I'm interested in trying out fprint.  However, when I try to
> download any of the source packages at
> http://people.freedesktop.org/~hadess/ I get the error: could not be
> saved, because the source file could not be read.

Both working as expected here.
Brent Oster | 4 Jul 20:13 2011
Picon

Re: cannot download

Hmm, it's working now.  Not sure what the problem was... it was
probably on my end.  Thanks, though!

 - Brent

On Mon, Jul 4, 2011 at 1:20 PM, Bastien Nocera <hadess <at> hadess.net> wrote:
> On Mon, 2011-07-04 at 13:06 -0400, Brent Oster wrote:
>> Hi there, I'm interested in trying out fprint.  However, when I try to
>> download any of the source packages at
>> http://people.freedesktop.org/~hadess/ I get the error: could not be
>> saved, because the source file could not be read.
>
> Both working as expected here.
>
>
Chow Loong Jin | 4 Jul 21:42 2011

Re: RFC: [PATCH] BSAPI bridge driver for libfprint

Hello Luiz,

On 04/07/2011 10:47, Luiz Angelo Daros de Luca wrote:
> I can confirm that this also works with my device. Probably, it will
> work with any supported BSAPI devices.
> 
> I am not a fprint commiter and not a fprint master but I have some suggestions.
> 
> It should exists a way to switch from/to libfprint native driver
> to/from bsapi one. Maybe a env variable? Have the case of multiple
> drivers implementing the same device ever happened in fprint? Also, I
> think that native upek*.c drivers should have precedence over bsapi
> (if not set explicitily by env or compile flag)

Currently, the bsapi driver only activates when libbsapi.so is found. I believe
a valid assumption would be that people who have the proprietary libbsapi.so
installed would want the driver to override the native driver.

On the other hand, like you mentioned, an environment variable would be useful
to force the bsapi driver to not even try loading the library. I'll add support
for that in the discover() function.

> 
> The configure script may need some fix like checking for bsapi and
> disabling the driver if libs are missing. Configure also does not list
> the new driver in the drivers feedback (--with-drivers).

Ah, I missed that out in the configure script. I'll fix it up.

> --- libfprint/drivers/bsapi.c.old       2011-07-03 22:54:26.000000000 -0300
(Continue reading)

Rafael Toledo | 7 Jul 14:54 2011
Picon

Couldn't open device on Ubuntu 11.04

Hello there!


I'm trying to use the libfprint on Ubuntu 11.04, but when I try to open the device (Digital Persona u.are.u 4000B), I receive the following error message:

uru4000:error [dev_init] interface claim failed
fp:error [fp_dev_open] device initialisation failed, driver=uru4000

I tried to do the procedures described on this tutorial - http://bit.ly/dvtWB5 -, but I haven't any effect.
Do Anyone can help me?

Rafael Toledo
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Bastien Nocera | 7 Jul 14:59 2011
Picon

Re: Couldn't open device on Ubuntu 11.04

On Thu, 2011-07-07 at 09:54 -0300, Rafael Toledo wrote:
> Hello there!
> 
> 
> I'm trying to use the libfprint on Ubuntu 11.04, but when I try to
> open the device (Digital Persona u.are.u 4000B), I receive the
> following error message:
> 
> 
> uru4000:error [dev_init] interface claim failed
> fp:error [fp_dev_open] device initialisation failed, driver=uru4000
> 
> 
> I tried to do the procedures described on this tutorial
> - http://bit.ly/dvtWB5 -, but I haven't any effect.
> Do Anyone can help me?

This "procedure" is 3 years old, and completely out-dated. Install the
latest libfprint and fprintd. There's a PAM module shipped with fprintd.

Cheers
Rafael Toledo | 7 Jul 15:16 2011
Picon

Re: Couldn't open device on Ubuntu 11.04

I downloaded the last version of libfprint and fprintd from the git, recompiled my app, but the error remains the same.

_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Rafael Toledo | 7 Jul 15:22 2011
Picon

Re: Couldn't open device on Ubuntu 11.04

Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 05ba:000a DigitalPersona, Inc. Fingerprint Reader
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint

Gmane