mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Daniel Bonekeeper" <thehazard@gmail.com>
To: linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org
Subject: Re: Driver for Microsoft USB Fingerprint Reader
Date: Wed, 5 Jul 2006 12:32:38 -0400	[thread overview]
Message-ID: <e1e1d5f40607050932v2441aa0chd8a2aac31e0b6881@mail.gmail.com> (raw)

As I said before, usefulness is something relative, and sometimes,
security is not a concern (even when talking about fingerprint
readers).
My intention with this is to try to create a catalog of fingerprint
readers' properties and I think that taking a look at vendors' SDKs
would be a good start.
As pointed out by Greg, it would be also interesting to export those
properties via sysfs instead of structure passing (or in addiction,
not sure yet).
I'm not sure though about relating fingerprint devices with V4L2 (even
the cheapest ones). Some other considerations discussed with Greg are
also:

1) extending those device informations to other classes, not only to
fingerprint readers
2) maybe using another layer to hold device properties based on
classes ( device driver -> device information layer -> sysfs+kobjects
) so we can have specific properties for "fingerprintreader" objects
and easier ways to export them to the sysfs layer, without explicit
declaration on the device driver
3) extend that layer also to non-USB devices ( bus-independent )

Maybe sysfs classes could have a list of default properties (for
example, /sys/class/fingerprint objects could hold a list of commom
fingerprint properties).

Bill, which fingerprint reader are you using ?

Daniel

-- 
What this world needs is a good five-dollar plasma weapon.

             reply	other threads:[~2006-07-05 16:32 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-05 16:32 Daniel Bonekeeper [this message]
     [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
  -- strict thread matches above, loose matches on Subject: below --
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
2006-07-03  6:51 Daniel Bonekeeper
2006-07-03  8:52 ` Daniel Drake
2006-07-03 10:04 ` Alon Bar-Lev
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
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

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=e1e1d5f40607050932v2441aa0chd8a2aac31e0b6881@mail.gmail.com \
    --to=thehazard@gmail.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®