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 18:11:03 -0400 [thread overview]
Message-ID: <e1e1d5f40607031511l5445f338t449bf8840e8caf80@mail.gmail.com> (raw)
In-Reply-To: <20060703214509.GA5629@kroah.com>
On 7/3/06, Greg KH <greg@kroah.com> wrote:
> A: No.
> Q: Should I include quotations after my reply?
>
> On Mon, Jul 03, 2006 at 04:53:43PM -0400, Daniel Bonekeeper wrote:
> > hahahaha I wish I could... well, you are _always_ welcome to donate me
> > yours ! =P
> > I'll try more later to get one of those readers...
> >
> > Reading Greg's comment, now I'm in doubt if this should really be in
> > kernel mode or at userspace. Since there is no standard (AFAIK) for
> > those readers, how should it be done ?
>
> It all depends on what you want the userspace interface to be.
>
That's one problem: I don't want to create one more userspace
interface for that. I suppose that all the hundreds of fingerprint
readers that ships with a SDK have their own way of doing that.. that
looks awfull to me, even though I believe that currently there isn't
any uniform way of working with fingerprint readers... shouldn't we
have a way to classify devices ? For example, if I want to list all
the printers connected via USB (supposing that we have more than one),
I should be able to request that information from somewhere
(/dev/usb/printers/* ?) I suppose that different fingerprint readers
works with different resolutions... we should be able to have an
unified interface that could tell the userspace the capabilities of
each fingerprint device (the area size of the scanner, resolution,
etc)... I think that applies for a lot of devices, not just
fingerprint readers. Probably there is already something like that.
> > Another thing: where can I find documentation about the USB
> > architecture ?
>
> www.usb.org for the USB specs. See the kernel built-in documentation
> for a full document on how the Linux USB layer works.
Thanks... UTFG for me. #)
> > For example, I suppose that some (or all) USB devices may have DMA
> > capabilities... how is this done ?
>
> Heh, no, USB can't do DMA at all. Why would you think they could? It's
> a serial bus that just streams data across it at relativly slow speeds.
>
Well.. even though I didn't know how and was a bit suspicious, I used
to believe that USB devices could do DMA because I heard some time ago
about "the danger of USB devices that could do DMA and have total
access over the OS"... something on bugtraq or securityfocus...
talking about USB and FireWire devices and how they could be used to
"inject" stuff on the system's memory and take it over... but I guess
it only applies to firewire (even though USB was clearly mentioned).
Reviewing it, it definitely applies just for firewire stuff.
http://www.csoonline.com/read/050106/ipods.html
> thanks,
>
> greg k-h
>
--
What this world needs is a good five-dollar plasma weapon.
next prev parent reply other threads:[~2006-07-03 22:11 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 [this message]
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
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=e1e1d5f40607031511l5445f338t449bf8840e8caf80@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®