From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Richard Hughes <hughsient@gmail.com>,
Luming Yu <luming.yu@gmail.com>,
linux-acpi@vger.kernel.org
Subject: Re: [RFC PATCH] report acpi video hot key event through input device
Date: Wed, 1 Aug 2007 18:12:27 +0100 [thread overview]
Message-ID: <20070801171227.GA14874@srcf.ucam.org> (raw)
In-Reply-To: <d120d5000708010652h61028821w7ba869deb9686578@mail.gmail.com>
On Wed, Aug 01, 2007 at 09:52:47AM -0400, Dmitry Torokhov wrote:
> My position is that generic event reporting (such as something has
> already switched video output from LCD to CRT, network link lost,
> battery low, brightness has already been changed) are outside of input
> layer domain (it would be silly to attach struct input_dev to network
> cards, wouldn't it?).
I think that's an understandable position, but it's not one which
matches reality in some cases (sadly). Most Dells generate an i8042
scancode when you hit the brightness keys, even though they'll also
change the brightness. They'll do the same for the wireless killswitch.
Personally, I think it's logical for physical keys to generate events
though the input layer.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2007-08-01 17:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-29 16:40 [RFC PATCH] report acpi video hot key event through input device Luming Yu
2007-07-30 0:50 ` Matthew Garrett
2007-07-30 11:47 ` Richard Hughes
2007-07-30 12:55 ` Dmitry Torokhov
2007-07-31 12:58 ` Henrique de Moraes Holschuh
2007-08-01 13:52 ` Dmitry Torokhov
2007-08-01 14:59 ` Henrique de Moraes Holschuh
2007-08-01 17:12 ` Matthew Garrett [this message]
2007-08-08 6:37 ` Zhang Rui
2007-08-14 11:58 ` Richard Hughes
2007-08-14 10:43 ` [RFC PATCH] report acpi video hot key event through inputdevice Zhang Rui
2007-08-15 8:05 ` Zhang Rui
2007-08-08 18:08 ` [RFC PATCH] report acpi video hot key event through input device Zhang Rui
2007-08-08 6:32 ` Zhang Rui
2007-08-08 18:07 ` Zhang Rui
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=20070801171227.GA14874@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=hughsient@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=luming.yu@gmail.com \
/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.