All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Mattia Dongili <malattia@linux.it>
Cc: Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, Stelian Pop <stelian@popies.net>,
	Richard Hughes <richard@hughsie.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH 5/7] Make the driver use MSC_SCAN and a setkeycode and getkeycode key table.
Date: Sun, 15 Jul 2007 22:11:28 +0100	[thread overview]
Message-ID: <20070715211128.GA6291@srcf.ucam.org> (raw)
In-Reply-To: <11845208791511-git-send-email-malattia@linux.it>

On Mon, Jul 16, 2007 at 02:34:37AM +0900, Mattia Dongili wrote:
> +		/* we emit the scancode so we can always remap the key */
> +		input_event(kp.dev, EV_MSC, MSC_SCAN, event);

As I said to Henrique, I don't think this is the right solution. We know 
what these keys do - we should send the appropriate keycode, rather than 
asking userspace to remap it.
-- 
Matthew Garrett | mjg59@srcf.ucam.org

  parent reply	other threads:[~2007-07-15 21:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-15 17:34 [PATCH 0/7] sony-laptop for 2.6.23 (updated) Mattia Dongili
2007-07-15 17:34 ` [PATCH 1/7] sony-laptop: add new SNC handlers Mattia Dongili
2007-07-15 17:34   ` [PATCH 2/7] sony-laptop: map wireless switch events to KEY_WLAN Mattia Dongili
2007-07-15 17:34     ` [PATCH 3/7] Add support for recent Vaios Fn keys (C series for now) Mattia Dongili
2007-07-15 17:34       ` [PATCH 4/7] Invoke _INI for SNC devices that provide it Mattia Dongili
2007-07-15 17:34         ` [PATCH 5/7] Make the driver use MSC_SCAN and a setkeycode and getkeycode key table Mattia Dongili
2007-07-15 17:34           ` [PATCH 6/7] Add Vaio FE to the special init sequence Mattia Dongili
2007-07-15 17:34             ` [PATCH 7/7] Fix event reading in sony-laptop Mattia Dongili
2007-07-15 21:11           ` Matthew Garrett [this message]
2007-07-16 17:06             ` [PATCH 5/7] Make the driver use MSC_SCAN and a setkeycode and getkeycode key table Richard Hughes
2007-07-16 18:09               ` Matthew Garrett
2007-07-17 10:37                 ` Richard Hughes
2007-07-17 10:46                   ` Matthew Garrett
2007-07-18 11:45                   ` Mattia Dongili
2007-07-18 14:28                     ` Matthew Garrett
2007-07-18 15:05                       ` Dmitry Torokhov
2007-07-18 15:17                         ` Richard Hughes
2007-07-18 16:02                           ` Dmitry Torokhov
2007-07-18 16:20                             ` Richard Hughes
2007-07-18 16:25                           ` Matthew Garrett
2007-07-18 16:39                             ` Dmitry Torokhov
2007-07-18 16:44                             ` Richard Hughes
2007-07-18 16:56                               ` Matthew Garrett
2007-07-19 15:51                       ` Mattia Dongili
2007-07-16 13:22           ` Dmitry Torokhov
2007-07-18 11:33             ` Mattia Dongili
2007-07-19 17:01               ` Mattia Dongili
2007-07-22  4:36                 ` Len Brown
2007-07-18 11:45             ` Mattia Dongili
2007-07-22  4:37 ` [PATCH 0/7] sony-laptop for 2.6.23 (updated) Len Brown

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=20070715211128.GA6291@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=malattia@linux.it \
    --cc=richard@hughsie.com \
    --cc=stelian@popies.net \
    /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.