All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Enhanced Keyboard Driver
Date: Thu, 12 May 2005 21:39:17 +0200	[thread overview]
Message-ID: <20050512193917.GC8176@lug-owl.de> (raw)
In-Reply-To: <20050512192254.43538.qmail@web53101.mail.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]

On Thu, 2005-05-12 12:22:54 -0700, Alan Bryan <icemanind@yahoo.com> wrote:
> Would it be feasable to modify the current keyboard
> driver in such a way that it would log the last 1000
> keystrokes pushed (possibly log it somewhere in /proc
> or something)? When I say keystrokes, I mean
> everything...even the ctrl and alt and shift bit keys

That's simple if you do it in a hackish way, but maybe a bit different
to what you think. You'd extend the struct atkbd to contain a 1000 entry
array and in rolling index. Then stuff your current keypress into the
array and you're done.

You'd need to hack in the proc interface, though.

> Something like this would greatly simplify the program
> I am attempting to make.

What do you actually want to do?

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-05-12 19:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-12 19:22 Enhanced Keyboard Driver Alan Bryan
2005-05-12 19:39 ` Jan-Benedict Glaw [this message]
2005-05-12 19:48   ` Alan Bryan
2005-05-12 20:06     ` Xavier Bestel
2005-05-12 20:10     ` Joel Jaeggli
2005-05-12 20:26     ` Jan-Benedict Glaw
2005-05-12 20:45     ` Dmitry Torokhov
2005-05-12 19:51 ` 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=20050512193917.GC8176@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --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.