I've tried libusb, looks like it works more or less.
What is the right policy about libusb* libraries ?
I have security/libfprint (finger-print reader that uses ugen device)
that stop working after upgrade.
Following entry in /etc/libmap.conf make it works somehow
libusb-0.1.so libusb20.so
libusb-0.1.so.8 libusb20.so.1
It allows library to access usb device, but pam authentication with it
still does not work ( looks like it reads fingerprint correctly, but
fails later ).
What is right way to handle that situation ?
Is there universal library, that will work for both stacks ?
PS. I didn't try yet libgphoto2 (it also uses ugen directly).
--
Vladimir B. Grebenschikov
vo...@fbsd.ru
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"
Have you checked the permissions of your device?
usbconfig dump_access
>
> What is right way to handle that situation ?
> Is there universal library, that will work for both stacks ?
I was thinking about doing some detection inside libusb in ports, but
currently you have to switch manually. On problem is that the libusb code in
ports is not BSD licensed, so we cannot just copy in the old UGEN support :-(
/*
* (Free|Open|Net)BSD USB support
*
* Derived from Linux version by Richard Tobin.
*
* $Id: bsd.c,v 1.33 2006/03/04 01:16:10 jerdfelt Exp $
* $Name: $
*
* This library is covered by the LGPL, read LICENSE for details.
*/
On the other hand, libusbhid, automatically detects USB stack and switches
everything accordingly.
> PS. I didn't try yet libgphoto2 (it also uses ugen directly).
--HPS
> > I have security/libfprint (finger-print reader that uses ugen device)
> > that stop working after upgrade.
> >
> > Following entry in /etc/libmap.conf make it works somehow
> > libusb-0.1.so libusb20.so
> > libusb-0.1.so.8 libusb20.so.1
> >
> > It allows library to access usb device, but pam authentication with it
> > still does not work ( looks like it reads fingerprint correctly, but
> > fails later ).
>
> Have you checked the permissions of your device?
>
> usbconfig dump_access
I guess problem is not in access, it reads device
$ sudo -s
Scan right ring finger on UPEK TouchStrip
>>> it founds chip
Scan didn't quite work. Please try again.
>>> wrong scan
Scan right ring finger on UPEK TouchStrip
>>> good scan, and some kind of failure here
Password:
sudo: pam_authenticate: conversation failure
$
# usbconfig -u 3 -a 3 dump_access
Global Access: root:operator 0660
ugen3.3: <Biometric Coprocessor STMicroelectronics> at usbus3, cfg=0
md=HOST spd=FULL (12Mbps) pwr=ON
Device Access: operator:operator 0660
Interface 0 Access: <not set>
#
(I am in operator group)
> >
> > What is right way to handle that situation ?
> > Is there universal library, that will work for both stacks ?
>
> I was thinking about doing some detection inside libusb in ports, but
> currently you have to switch manually. On problem is that the libusb code in
> ports is not BSD licensed, so we cannot just copy in the old UGEN support :-(
Probably we may provide patch against devel/libusb to depend it on
libusb20 ?
So devel/libusb will stay LGPLed but libusb20 will be BSD licensed ?
--
Vladimir B. Grebenschikov
vo...@fbsd.ru
Hi,
>
> Probably we may provide patch against devel/libusb to depend it on
> libusb20 ?
Yes. I don't know about such a patch yet, but this is something that needs to
be done for -current .
> So devel/libusb will stay LGPLed but libusb20 will be BSD licensed ?
I think that is the case.
--HPS
> On Wednesday 04 February 2009, Vladimir Grebenschikov wrote:
>> On Wed, 2009-02-04 at 10:49 +0100, Hans Petter Selasky wrote:
>>
>> Probably we may provide patch against devel/libusb to depend it on
>> libusb20 ?
>
> Yes. I don't know about such a patch yet, but this is something that
> needs to
> be done for -current.
Could we get a pkg-config definition file for libusb20 in the base
system or in the libusb port? I have come up with my own for my
systems (See below). There's a plethora of configure scripts that
depend on pkg-config to do the right thing WRT libusb...
# -- 8< --
# Package Information for pkg-config
prefix=/usr/
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
Name: libusb
Description: libusb 2.0
Version: 2.0
Libs: -L${libdir} -lusb20
Cflags: -I${includedir}
# -- 8< --
Cheers,
Andy
/* Andre Guibert de Bruet * 436f 6465 2070 6f65 742e 2042 6974 206a */
/* Managing Partner * 6f63 6b65 792e 2053 7973 4164 6d69 6e2e */
/* GSM: +1 734 846 8758 * 2055 4e49 5820 736c 6575 7468 2e00 0000 */
/* WWW: siliconlandmark.com * C/C++, Java, Perl, PHP, SQL, XHTML, XML */