From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-input@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: Extra keycodes
Date: Fri, 24 Feb 2006 23:00:58 -0500 [thread overview]
Message-ID: <200602242300.58815.dtor_core@ameritech.net> (raw)
In-Reply-To: <20060223175328.GA25482@srcf.ucam.org>
On Thursday 23 February 2006 12:53, Matthew Garrett wrote:
> Hi,
>
> Several laptops have keys that are intended to show battery status. In
> order to present a consistent view to userspace, it would be nice to
> have a standard keycode to map them to. linux/input.h doesn't currently
> provide anything appropriate. What's the correct way of allocating
> another keycode?
>
Just post a patch adding it to input.h and we'll discuss... Who is intended
user? What interface is expected to be used (evdev)?
--
Dmitry
next prev parent reply other threads:[~2006-02-25 4:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 17:53 Extra keycodes Matthew Garrett
2006-02-25 4:00 ` Dmitry Torokhov [this message]
2006-02-26 16:07 ` Matthew Garrett
2006-03-08 17:37 ` Matthew Garrett
2006-03-08 18:01 ` 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=200602242300.58815.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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