From: Erich Schubert <erich.schubert@mucl.de>
To: Francis Galiegue <fg@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compaq Presario Notebook Keyboard "Extensions"
Date: Fri, 14 Sep 2001 13:14:01 +0200 [thread overview]
Message-ID: <20010914131401.A27166@erich.xmldesign.de> (raw)
In-Reply-To: <20010913124623.A22927@erich.xmldesign.de> <Pine.LNX.4.30.0109141126560.1617-100000@toy.mandrakesoft.com>
In-Reply-To: <Pine.LNX.4.30.0109141126560.1617-100000@toy.mandrakesoft.com>
> anything. On all desktop PC keyboards that I could lay my hands on
> otherwise, it generates e0 xx scancodes on press and e0 (xx | 0x80) on
> release. Some of these scancodes even seem to be standard (volume up and
> down, play and pause key...). I made a dedicated driver to handle these
> keys for 2.2 already. Not yet ported to 2.4.
You don't need a driver for them at all.
I had been playing with such a driver (for 2.2) which redirect a
configurable set of keys to a special device /dev/funkey or thelike.
Well, i'm not missing this patch now, there's a great tool called
"hotkeys" for X (available as debian package hotkeys) which has an X11
On-Screen-Display for Volume, predefined mappings for most keyboards and
is really easy to customize. I use that for controlling volume and xmms,
as well as launching some apps. (a "new terminal" hotkey is great ;)
Doesn't help here though - it needs scancodes.
Greetings,
Erich
prev parent reply other threads:[~2001-09-14 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 10:46 Compaq Presario Notebook Keyboard "Extensions" Erich Schubert
2001-09-14 15:34 ` Francis Galiegue
2001-09-14 11:14 ` Erich Schubert [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=20010914131401.A27166@erich.xmldesign.de \
--to=erich.schubert@mucl.de \
--cc=fg@mandrakesoft.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).