All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Leonard Milcin Jr." <leonard.milcin@post.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: keyboard driver of 2.6 kernel
Date: Wed, 04 Jan 2006 10:07:59 +0100	[thread overview]
Message-ID: <43BB906F.3010900@post.pl> (raw)
In-Reply-To: <1136363622.2839.6.camel@laptopd505.fenrus.org>

Arjan van de Ven 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!

Let's pretend it's some sort of auditing ;-)


Leonard Milcin Jr.


  reply	other threads:[~2006-01-04  9:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04  8:32 keyboard driver of 2.6 kernel P.Manohar
2006-01-04  8:33 ` Arjan van de Ven
2006-01-04  9:07   ` Leonard Milcin Jr. [this message]
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

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=43BB906F.3010900@post.pl \
    --to=leonard.milcin@post.pl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.