From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "P.Manohar" <pmanohar@lantana.tenet.res.in>,
linux-kernel@vger.kernel.org
Subject: Re: keyboard driver of 2.6 kernel
Date: Wed, 4 Jan 2006 11:25:00 -0500 [thread overview]
Message-ID: <d120d5000601040825m1ee3f994g8ae45ca30819a7ae@mail.gmail.com> (raw)
In-Reply-To: <1136363622.2839.6.camel@laptopd505.fenrus.org>
On 1/4/06, Arjan van de Ven <arjan@infradead.org> wrote:
> On Wed, 2006-01-04 at 14:02 +0530, P.Manohar wrote:
> > Greetings,
> > I have a small doubt in Linux kernel keyboard driver.
> > In 2.4 kernels the starting fuction of keyboard driver is "handle_scancode".
> > But in 2.6 kernels the keyboard interface
> > is changed drastically. If you familiar with that can you tell me the starting
> > fuction of keyboard interace which gets
> > the scancodes in 2.6 kernels.
> >
> > Actually my paln is to stuff scancodes or keycodes to the keyboard buffer
> > , from there on the keyboard driver processes them. I have done this for
> > 2.4 kernel. I want to implement the same to 2.6 kernel.
> >
> > Is there any keyloggers which are implemented for 2.6 kernels?
>
> this is not r00tkitnewbies mailing list
>
> keyloggers are evil!
>
Anyway, if you want to read keypresses and other input events use
corresponding event device (/dev/input/eventX). If you want to feed
input events into the kernel you need to use "uinput" driver.
--
Dmitry
prev parent reply other threads:[~2006-01-04 16:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 8:32 P.Manohar
2006-01-04 8:33 ` Arjan van de Ven
2006-01-04 9:07 ` Leonard Milcin Jr.
2006-01-04 9:23 ` Jan Engelhardt
2006-01-05 10:08 ` [OT] " Roberto Nibali
2006-01-05 11:51 ` Jan Engelhardt
2006-01-05 12:43 ` Roberto Nibali
2006-01-05 21:07 ` Nuno Monteiro
2006-01-05 23:28 ` Roberto Nibali
2006-01-06 7:01 ` Jan Engelhardt
2006-01-06 10:28 ` Nuno Monteiro
2006-01-05 11:58 ` Leonard Milcin Jr.
2006-01-05 12:47 ` Roberto Nibali
2006-01-04 16:25 ` Dmitry Torokhov [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=d120d5000601040825m1ee3f994g8ae45ca30819a7ae@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=arjan@infradead.org \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pmanohar@lantana.tenet.res.in \
/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®