From: "Daniel Bonekeeper" <thehazard@gmail.com>
To: "Greg KH" <greg@kroah.com>
Cc: "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: Mon, 3 Jul 2006 19:24:30 -0400 [thread overview]
Message-ID: <e1e1d5f40607031624w245e5f70g2ae8f5d0e9d357c4@mail.gmail.com> (raw)
In-Reply-To: <20060703222645.GA22855@kroah.com>
I think that I didn't make myself clear on that... let me try to
explain on what I'm thinking to do. Let's take as example Dan's driver
at http://prdownload.berlios.de/dpfp/dpfp-driver-0.1.2.tar.bz2.
On our usb_device_id, we specify the vendor of the device, etc. We
could also (I don't know if this is the best place to do that) specify
which kind of device is it (printer, storage, fingerprint reader, HID,
etc). Let's suppose that we have some #define's or a enum that specify
the hundreds of different device types (is that possible ? :) Nothing
that a USB_GENERIC can't solve lol).
enum usb_device_type {
USB_DEVICE_SCANNER,
USB_DEVICE_KEYBOARD,
USB_DEVICE_MOUSE,
USB_DEVICE_FINGERPRINT_READER,
USB_DEVICE_GENERIC,
...
};
For each device, he have some kind of struct that is complex enough to
describe characteristics of each device, at least the most common
ones. So, for USB_DEVICE_FINGERPRINT_READER, we could have:
#define FINGEPRINT_IMAGE_JPG 0
#define FINGEPRINT_IMAGE_PNM 1
#define FINGEPRINT_IMAGE_BMP 2
#define FINGEPRINT_IMAGE_RAW 3
struct usb_devcap_fingerprint_reader {
unsigned int width;
unsigned int height;
unsigned int colors;
unsigned char cap_encrypted_output;
unsigned char image_type; /* FINGEPRINT_IMAGE_PNM */
};
(I know, this sucks, but you got the idea).
So our usb_device_id array could also include the kind of device and a
pointer to our structure describing the device capabilities, something
like:
static struct usb_devcap_fingerprint_reader
usb_devcap_fingerprint_reader_mskeyboard = {
.width = 100,
.height = 100,
.colors = 2,
.cap_encrypted_output = 0,
.image_type = FINGEPRINT_IMAGE_BMP,
}
static struct usb_device_id dpfp_table[] = {
{
/* Microsoft Keyboard with Fingerprint reader */
USB_DEVICE(0x045e, 0x00bb),
.driver_info = DPFP_TYPE_URU4000B,
USB_DEVICE_FINGERPRINT_READER,
(usb_devcap_fingerprint_reader *) usb_devcap_fingerprint_reader_mskeyboard,
},
{} /* terminating null entry */
};
So, to know each fingerprint reader device (if any) and its
capabilities, we could have a directory like /dev/usb/fingerprint
where we could iterate and access the device thru
/dev/usb/fingerprint/fingerprint0. Opening a fd to this device and
issuing a ioctl(), we could have a usb_devcap_fingerprint_reader-like
structure on userspace filled in with the device's capabilities, so we
would know exactly what to expect when doing a cat
/dev/usb/fingerprint/fingerprint0 > /tmp/catchme.bmp.
I think that the most difficult part would be summarize the thousands
of different devices and their capabilities in a struct ()... but I
also think that this stuff is needed, and should be kept by the
kernel, and not some lib in userspace...
Daniel
--
What this world needs is a good five-dollar plasma weapon.
next prev parent reply other threads:[~2006-07-03 23:24 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
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 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 [this message]
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
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=e1e1d5f40607031624w245e5f70g2ae8f5d0e9d357c4@mail.gmail.com \
--to=thehazard@gmail.com \
--cc=alon.barlev@gmail.com \
--cc=greg@kroah.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®