[fprint] AES1660: AES2660: call for testers
Vasily Khoruzhick
anarsoul at gmail.com
Sun Nov 25 10:34:52 PST 2012
Hi all,
It's 3rd testing round for AES1660 owners.
And 1st for AES2660 owners :)
BIG FAT WARNING: PLEASE KEEP FPRINT MAILLIST IN CC!
New code is in aesx660-dev branch. Almost no changes for AES1660 owners.
This branch intoduces AES2660 driver, and this driver shares almost
all code with
AES1660. So I want to ensure that code reorganization did not break
anything for AES1660.
To obtain it:
1. if you already cloned my repo:
cd libfprint
git checkout master
git pull
git checkout -b aesx660-dev origin/aesx660-dev
2. Fresh clone:
git clone git://github.com/anarsoul/libfprint.git
cd libfprint
git checkout -b aesx660-dev origin/aesx660-dev
Use instructions from my previous post [1] to compile and test it.
Regards
Vasily
[1] http://lists.freedesktop.org/archives/fprint/2012-November/000330.html
> Hi,
>
> This is another call for testing.
>
> BIG FAT WARNING: PLEASE KEEP FPRINT MAILLIST IN CC!
>
> I've just pushed improved aes1660 driver into aes1660-dev-v2 branch of
> my libfprint repo on github.
> This one mimics windows driver behavior completely (and works much
> better for me!).
>
> To obtain it:
>
> 1. if you already cloned my repo:
> cd libfprint
> git checkout master
> git pull
> git checkout -b aes1660-dev-v2 origin/aes1660-dev-v2
>
> 2. Fresh clone:
> git clone git://github.com/anarsoul/libfprint.git
> cd libfprint
> git checkout -b aes1660-dev-v2 origin/aes1660-dev-v2
>
> Use instructions from my previous post to compile and test it.
>
> Regards
> Vasily
>
> On Sun, Nov 18, 2012 at 12:01 PM, Vasily Khoruzhick <anarsoul at gmail.com> wrote:
>> Hi,
>>
>> I've just pushed aes1660 driver code into my libfprint github repo,
>> branch aes1660-dev,
>> so it would be nice to get some testing reports from AES1660-owners :)
>>
>> To get it do:
>>
>> git clone git://github.com/anarsoul/libfprint.git
>> cd libfprint
>> git checkout -b aes1660-dev origin/aes1660-dev
>>
>> Install fprint_demo from your distro repos, and then install libfprint into home
>>
>> ./autogen.sh
>> ./configure --prefix=/home/your_user/usr --enable-debug-log
>> make -j4
>> make install # No sudo here!
>>
>> And then try fprint_demo:
>>
>> export LD_LIBRARY_PATH=/home/your_user/usr/lib
>> fprint_demo
>>
>> If your user have no enough permissions do:
>>
>> sudo su
>> export LD_LIBRARY_PATH=/home/your_user/usr/lib
>> fprint_demo
>>
>> If it crashes, or does not work properly for you collect and send me
>> debug logs from console while running fprint_demo
>>
>> Regards
>> Vasily
More information about the fprint
mailing list