From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jeremy Katz <katzj@redhat.com>,
linux-kernel@vger.kernel.org, davej@redhat.com
Subject: Re: [PATCH] Map volume and brightness events on thinkpads
Date: Tue, 23 Oct 2007 21:34:03 -0200 [thread overview]
Message-ID: <20071023233403.GD8224@khazad-dum.debian.net> (raw)
In-Reply-To: <d120d5000710230854j28502be6xd5a0fd8d2fab3b77@mail.gmail.com>
On Tue, 23 Oct 2007, Dmitry Torokhov wrote:
> in question. Probably simply adding separate key notify events (such
> as KEY_BRIGHTNESSUP_NOTIFY) to EV_KEY instead of creating EV_NOTIFY is
> not such a bad idea - this way we can fix keymap from userspace (if
> needed) instead of needing to modify the krenel.
That is a killer argument for EV_KEY over EV_NOTIFY if I have ever seen one.
> So, EV_KEY (and extending KEY_MAX to 1024) or EV_NOTIFY?
EV_KEY, please.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2007-10-23 23:34 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 20:45 [PATCH] Map volume and brightness events on thinkpads Jeremy Katz
2007-10-15 21:07 ` Henrique de Moraes Holschuh
2007-10-15 21:27 ` Jeremy Katz
2007-10-16 9:12 ` Henrique de Moraes Holschuh
2007-10-15 21:43 ` Arjan van de Ven
2007-10-16 3:38 ` Jesse Barnes
2007-10-16 8:36 ` Henrique de Moraes Holschuh
2007-10-16 8:49 ` Jesse Barnes
2007-10-16 9:18 ` Henrique de Moraes Holschuh
2007-10-17 2:40 ` Jesse Barnes
2007-10-17 6:25 ` Henrique de Moraes Holschuh
2007-10-17 6:32 ` Jesse Barnes
2007-10-17 6:39 ` Henrique de Moraes Holschuh
2007-10-16 13:00 ` Matthew Garrett
2007-10-16 14:11 ` Henrique de Moraes Holschuh
2007-10-16 14:21 ` Matthew Garrett
2007-10-16 14:31 ` Henrique de Moraes Holschuh
2007-10-16 14:40 ` Matthew Garrett
2007-10-16 16:56 ` Henrique de Moraes Holschuh
2007-10-16 18:46 ` Matthew Garrett
2007-10-16 19:14 ` Linus Torvalds
2007-10-16 19:20 ` Matthew Garrett
2007-10-16 20:02 ` Henrique de Moraes Holschuh
2007-10-16 20:15 ` Dmitry Torokhov
2007-10-16 20:12 ` Dmitry Torokhov
2007-10-16 20:11 ` Jeremy Katz
2007-10-16 20:19 ` Dmitry Torokhov
2007-10-16 20:32 ` Linus Torvalds
2007-10-17 15:57 ` Dmitry Torokhov
2007-10-17 16:28 ` Matthew Garrett
2007-10-17 17:35 ` Henrique de Moraes Holschuh
2007-10-17 18:59 ` Dmitry Torokhov
2007-10-17 20:42 ` Henrique de Moraes Holschuh
2007-10-18 14:37 ` Dmitry Torokhov
2007-10-18 22:39 ` Henrique de Moraes Holschuh
2007-10-23 15:54 ` Dmitry Torokhov
2007-10-23 23:34 ` Henrique de Moraes Holschuh [this message]
2007-10-16 20:48 ` Kok, Auke
2007-10-16 20:55 ` Matthew Garrett
2007-10-16 21:18 ` Dmitry Torokhov
2007-10-16 20:32 ` Dave Airlie
2007-10-16 14:27 ` Dmitry Torokhov
2007-10-16 14:54 ` Matthew Garrett
2007-10-16 15:54 ` Dmitry Torokhov
2007-10-16 15:59 ` Matthew Garrett
2007-10-16 18:53 ` Matthew Garrett
2007-10-16 19:23 ` Renato S. Yamane
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=20071023233403.GD8224@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=davej@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=katzj@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=torvalds@linux-foundation.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