From: Matthew Garrett <mjg59@srcf.ucam.org>
To: linux-kernel@vger.kernel.org
Cc: dtor_core@ameritech.net
Subject: Telling the kernel that keys need soft release?
Date: Tue, 25 Apr 2006 21:25:26 +0100 [thread overview]
Message-ID: <20060425202526.GA29169@srcf.ucam.org> (raw)
Dell laptops have hotkeys on the top of the keyboard for "hibernate",
"cd eject", "battery status" and so on. These can be mapped to
appropriate keycodes, and life is good except for the fact that they
never produce a key release event. The kernel appears to have code to
deal with this for the hangul key, but it's hardcoded rather than
generic.
Is there any way for userspace to tell the event layer that a certain
keycode should have soft-release? If not, would a patch for this be
accepted?
--
Matthew Garrett | mjg59@srcf.ucam.org
next reply other threads:[~2006-04-25 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 20:25 Matthew Garrett [this message]
2006-04-25 20:33 ` Telling the kernel that keys need soft release? Dmitry Torokhov
2006-04-25 20:37 ` Matthew Garrett
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=20060425202526.GA29169@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=dtor_core@ameritech.net \
--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