From: Bill Davidsen <davidsen@tmr.com>
To: Florian Festi <florian@festi.info>,
Linux Kernel mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Meaning of keycodes unclear
Date: Tue, 05 Dec 2006 15:13:25 -0500 [thread overview]
Message-ID: <4575D2E5.3000401@tmr.com> (raw)
In-Reply-To: <45753BB1.6030102@festi.info>
Florian Festi wrote:
> I am looking for the meaning of the following key codes as #defined in
> include/linux/input.h. I need to know what hardware produces the keycode
> and what happens/should happen when the corresponding key is pressed.
> KEY_MACRO
I presume this is the macro defining key, used on keyboards like the
Gateway102. I thought it was handled internally and didn't send a
keycode, but other keyboards had/have that feature as well.
Used G102 for application work, had the function keys both next-to and
above the alpha keys, so you could bind up to 48 application functions
and still have function keys as other things wanted them.
Hope that answers your question.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2006-12-05 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 9:28 Meaning of keycodes unclear Florian Festi
2006-12-05 11:15 ` Pavel Machek
2006-12-05 14:23 ` Johannes Stezenbach
2006-12-05 20:13 ` Bill Davidsen [this message]
2006-12-14 15:09 ` Florian Festi
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=4575D2E5.3000401@tmr.com \
--to=davidsen@tmr.com \
--cc=florian@festi.info \
--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