From: Pavel Machek <pavel@ucw.cz>
To: Nelson Castillo <nelsoneci@gmail.com>, dmitry@ucw.cz
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Module for keyboard statistics / What should I look at?
Date: Sun, 2 Dec 2007 19:28:08 +0000 [thread overview]
Message-ID: <20071202192808.GA5538@ucw.cz> (raw)
In-Reply-To: <2accc2ff0711271707o636c060ck7587a259dab92917@mail.gmail.com>
On Tue 2007-11-27 20:07:16, Nelson Castillo wrote:
> Hi.
>
> More than 2 years ago I wrote a small non-portable patch [1] to gather
> some statistics
> about keyboard usage[2] ( I show the counters with modulo 10 but still this is a
> security risk. Perhaps some random noise should be added ).
RSI prevention?
> My questions are:
>
> * What should I read to do this in a module?
> * Is there a better way to to this? (perhaps using /dev/input/... and
> a user-space program) ?
Yep, I think you should be using /dev/input.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2007-12-03 19:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 1:07 Module for keyboard statistics / What should I look at? Nelson Castillo
2007-12-02 19:28 ` Pavel Machek [this message]
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=20071202192808.GA5538@ucw.cz \
--to=pavel@ucw.cz \
--cc=dmitry@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=nelsoneci@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox