public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Lammerts <eric@lammerts.org>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org, lineak-devel@lists.sourceforge.net
Subject: Re: Linux input event extending tool exist?
Date: Wed, 15 Dec 2004 23:41:38 -0500	[thread overview]
Message-ID: <41C11202.2040009@lammerts.org> (raw)
In-Reply-To: <20041210142044.GB20511@ucw.cz>

Vojtech Pavlik wrote:
> You can use evtest (attached). It's often found in the joystick RPMs.
> It's also in the linuxconsole.sf.net CVS repository.  On recent kernels
> it'll show the scancodes as well as the generated keycodes.

Vojtech, are you aware that this doesn't work well with 32-bit apps on 
x86-64 kernels? The ioctls don't work (no compat definitions), and 
struct input_event is 24 bytes instead of 16.

Eric

  reply	other threads:[~2004-12-16  4:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-10 14:38 Linux input event extending tool exist? Aivils
2004-12-10 14:20 ` Vojtech Pavlik
2004-12-16  4:41   ` Eric Lammerts [this message]
2004-12-16  8:34     ` Vojtech Pavlik
2005-02-06 18:41     ` Vojtech Pavlik

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=41C11202.2040009@lammerts.org \
    --to=eric@lammerts.org \
    --cc=lineak-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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