From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Daniel Bonekeeper <thehazard@gmail.com>
Cc: Greg KH <greg@kroah.com>, Alon Bar-Lev <alon.barlev@gmail.com>,
kernelnewbies@nl.linux.org, linux-kernel@vger.kernel.org
Subject: Re: Driver for Microsoft USB Fingerprint Reader
Date: Tue, 04 Jul 2006 09:39:30 +0100 [thread overview]
Message-ID: <1152002370.28597.9.camel@localhost.localdomain> (raw)
In-Reply-To: <e1e1d5f40607031549w734c82f4h28bb887709c32f44@mail.gmail.com>
Ar Llu, 2006-07-03 am 18:49 -0400, ysgrifennodd Daniel Bonekeeper:
> At least they have something in common: all of them deliver an image
> as output. Maybe that could be centralized somehow... for example, a
Not even that.
For those that do we have the video4linux API ("its just a bad webcam")
for the smartcard type devices the interfaces are generally unrelated.
> How does encryption-based readers works ? I suppose that a software
> driver or library in userspace should be responsible for decrypting
> the image and processing it, right ?
Usually you pick a combination of recognition algorithm and algorithm
that makes the per data unique per chip such that the recognition
algorithm can compare two sets of scrambled data.
next prev parent reply other threads:[~2006-07-04 8:22 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 6:51 Driver for Microsoft USB Fingerprint Reader Daniel Bonekeeper
2006-07-03 8:52 ` Daniel Drake
2006-07-03 10:04 ` Alon Bar-Lev
2006-07-03 17:37 ` [OT] " Alistair John Strachan
2006-07-03 20:16 ` Jan Engelhardt
2006-07-03 18:04 ` Daniel Bonekeeper
2006-07-03 18:16 ` Alon Bar-Lev
2006-07-03 20:53 ` Daniel Bonekeeper
2006-07-03 21:45 ` Greg KH
2006-07-03 22:11 ` Daniel Bonekeeper
2006-07-03 22:26 ` Greg KH
2006-07-03 23:24 ` Daniel Bonekeeper
2006-07-03 23:29 ` Greg KH
2006-07-04 0:04 ` Daniel Bonekeeper
2006-07-04 0:13 ` Greg KH
2006-07-05 17:58 ` Daniel Drake
2006-07-05 18:09 ` Daniel Bonekeeper
2006-07-05 18:55 ` Daniel Drake
2006-07-05 19:46 ` Daniel Bonekeeper
2006-07-05 23:23 ` Daniel Drake
2006-07-06 2:05 ` Daniel Bonekeeper
2006-07-06 10:35 ` Daniel Drake
2006-07-04 3:56 ` Daniel Bonekeeper
2006-07-04 3:58 ` Greg KH
2006-07-03 22:35 ` Alan Cox
2006-07-03 22:49 ` Daniel Bonekeeper
2006-07-04 8:39 ` Alan Cox [this message]
2006-07-05 4:01 ` Bill Davidsen
2006-07-05 15:55 ` Daniel Bonekeeper
2006-07-03 11:44 ` Alon Bar-Lev
2006-07-03 15:00 ` Valdis.Kletnieks
2006-07-03 17:09 ` Alon Bar-Lev
-- strict thread matches above, loose matches on Subject: below --
2006-07-05 16:32 Daniel Bonekeeper
2006-07-06 4:48 linux
2006-07-06 12:26 ` Daniel Drake
2006-07-06 17:38 ` Alan Cox
2006-07-06 17:49 ` Joel Jaeggli
[not found] <6vtYr-w2-5@gated-at.bofh.it>
[not found] ` <6vFQ5-1iV-71@gated-at.bofh.it>
2006-07-06 21:39 ` Bodo Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1152002370.28597.9.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alon.barlev@gmail.com \
--cc=greg@kroah.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thehazard@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.