From: Dmitry Torokhov <dtor@insightbb.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Richard Hughes <hughsient@gmail.com>,
Bastien Nocera <hadess@hadess.net>,
John Belmonte <john@neggie.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: Add INPUT support to toshiba_acpi
Date: Sun, 3 Jun 2007 00:48:39 -0400 [thread overview]
Message-ID: <200706030048.40393.dtor@insightbb.com> (raw)
In-Reply-To: <20070602142333.GA3452@srcf.ucam.org>
On Saturday 02 June 2007 10:23, Matthew Garrett wrote:
> On Sat, Jun 02, 2007 at 01:50:52PM +0100, Richard Hughes wrote:
> > > KEY_SCREENLOCK? KEY_SCREENSAVER?
> >
> > Either of these keys would be good to add.
>
> We've been interpreting "KEY_COFFEE" as screenlock (as in "I've gone for
> a coffee break, lock the screen").
>
It looks like KEY_COFFE comes from 0x0c/0x19e - AL Terminal Lock/Screensaver
so your interpretation is indeed correct. I guess I better add an alias to
input.h
--
Dmitry
next prev parent reply other threads:[~2007-06-03 4:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 12:36 Add INPUT support to toshiba_acpi Richard Hughes
2007-05-31 12:53 ` Bastien Nocera
2007-05-31 13:43 ` Richard Hughes
2007-05-31 15:46 ` Richard Hughes
2007-05-31 16:46 ` Andreas Mohr
2007-05-31 23:09 ` Richard Hughes
2007-06-01 16:45 ` Dmitry Torokhov
2007-06-02 12:50 ` Richard Hughes
2007-06-02 14:23 ` Matthew Garrett
2007-06-03 4:48 ` Dmitry Torokhov [this message]
2007-06-07 16:58 ` Richard Hughes
2007-06-08 14:23 ` Dmitry Torokhov
2007-06-08 14:30 ` Richard Hughes
2007-06-11 13:26 ` Renato S. Yamane
2007-06-23 14:56 ` Rolf Eike Beer
2007-06-25 9:52 ` Richard Hughes
2007-06-25 11:03 ` Rolf Eike Beer
2007-06-26 5:03 ` Rolf Eike Beer
2007-06-26 8:56 ` Richard Hughes
2007-06-28 11:27 ` Rolf Eike Beer
2007-06-28 12:22 ` Renato S. Yamane
2007-07-03 5:38 ` Rolf Eike Beer
2007-07-03 12:59 ` Renato S. Yamane
-- strict thread matches above, loose matches on Subject: below --
2007-11-06 18:54 Andrey Borzenkov
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=200706030048.40393.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=hadess@hadess.net \
--cc=hughsient@gmail.com \
--cc=john@neggie.net \
--cc=linux-acpi@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.