All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yu Luming <luming.yu@gmail.com>
To: Dmitry Torokhov <dtor@insightbb.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	Alessandro Guido <alessandro.guido@gmail.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	len.brown@intel.com, jengelh@linux01.gwdg.de, gelma@gelma.net,
	ismail@pardus.org.tr
Subject: Re: [PATCH 2.6.18-mm2] acpi: add backlight support to the sony_acpi driver
Date: Thu, 12 Oct 2006 00:48:19 +0800	[thread overview]
Message-ID: <200610120048.19953.luming.yu@gmail.com> (raw)
In-Reply-To: <200610102320.13952.dtor@insightbb.com>

> > It would have to be DMI-based to some extent - not all Sonys use the
> > same keys for the same purpose. Misery ensues.
>
> Then we need to add keymap table to the sonypi's input device so that
> keymap can be changed from userspace.
If some key is physically broken, I agree configurable keymap is the only 
solution. But, I don't see any other benefit of doing so, if we expect 
platform specific driver report meaningful key code to input layer.

Thanks,
Luming

  reply	other threads:[~2006-10-11 16:49 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-30 17:08 [PATCH 2.6.18-mm2] acpi: add backlight support to the sony_acpi driver Alessandro Guido
2006-09-30 17:14 ` Alessandro Guido
2006-09-30 17:31   ` Jan Engelhardt
2006-10-02  0:19 ` Andrew Morton
2006-10-02  0:39   ` Matt Domsch
2006-10-02  0:48     ` Matt Domsch
2006-10-05 10:36     ` Pavel Machek
2006-10-06 21:17       ` Matt Domsch
2006-10-06 22:44         ` Pavel Machek
2006-10-10 14:32         ` Yu Luming
2006-10-10 14:47           ` Richard Hughes
2006-10-10 16:10             ` Matt Domsch
2006-10-11 16:28               ` Yu Luming
2006-10-16 17:45                 ` Yu Luming
2006-10-25  7:07                   ` Pavel Machek
2006-10-25 17:26                     ` Luming Yu
2006-10-27 17:24                       ` Luming Yu
2006-10-29 17:50                       ` Pavel Machek
2006-10-30 15:49                         ` Luming Yu
2006-10-25 17:27                     ` Luming Yu
2006-10-10 21:26           ` Matthew Garrett
2006-10-11  3:02             ` Matt Domsch
2006-10-11  3:16               ` Matthew Garrett
2006-10-11 16:37               ` Yu Luming
2006-10-11  6:59             ` Arjan van de Ven
2006-10-11  7:04               ` Matthew Garrett
2006-10-11  8:04                 ` Ismail Donmez
2006-10-11  8:04                   ` Ismail Donmez
2006-10-11  8:12                   ` Matthew Garrett
2006-10-11 16:31                   ` Yu Luming
2006-10-11 16:45                     ` Ismail Donmez
2006-10-02 10:29   ` Holger Macht
2006-10-02 11:25   ` Alessandro Guido
2006-10-10 15:17     ` Yu Luming
2006-10-10 15:22       ` Richard Hughes
2006-10-10 21:23       ` Matthew Garrett
2006-10-11  3:20         ` Dmitry Torokhov
2006-10-11 16:48           ` Yu Luming [this message]
2006-10-11 19:08             ` 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=200610120048.19953.luming.yu@gmail.com \
    --to=luming.yu@gmail.com \
    --cc=akpm@osdl.org \
    --cc=alessandro.guido@gmail.com \
    --cc=dtor@insightbb.com \
    --cc=gelma@gelma.net \
    --cc=ismail@pardus.org.tr \
    --cc=jengelh@linux01.gwdg.de \
    --cc=len.brown@intel.com \
    --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.