public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Richard Hughes <hughsient@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Mattia Dongili <malattia@linux.it>, Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, Stelian Pop <stelian@popies.net>,
	Richard Hughes <richard@hughsie.com>
Subject: Re: [PATCH 5/7] Make the driver use MSC_SCAN and a setkeycode and getkeycode key table.
Date: Wed, 18 Jul 2007 17:25:11 +0100	[thread overview]
Message-ID: <20070718162510.GA22975@srcf.ucam.org> (raw)
In-Reply-To: <1184771822.14062.2.camel@work>

On Wed, Jul 18, 2007 at 04:17:02PM +0100, Richard Hughes wrote:
> On Wed, 2007-07-18 at 11:05 -0400, Dmitry Torokhov wrote:
> > 
> > I think we should continue adding keymaps to kernel until everyone is
> > using HAL's facilities to load keymaps and then stop. Does this make
> > sense? 
> 
> I don't think so. The whole idea of hal-info is that we can update a 14k
> noarch package every week if needed, that will work on pretty much any
> hal version.
> 
> I'm not sure people running FC3 systems are going to be running git
> kernels for new keymaps.

This isn't an either/or situation. If you have a hal keymap then the 
system will still work. The question is what to do in the absence of 
hal. The kernel can either provide sane defaults (that might be wrong in 
a couple of cases) or it can provide keys that are pretty much 
guaranteed to do nothing. I think doing our best to make things work 
even if hal isn't there is sensible - if hal /is/ there, we've lost 
nothing.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  parent reply	other threads:[~2007-07-18 16:25 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           ` [PATCH 5/7] Make the driver use MSC_SCAN and a setkeycode and getkeycode key table Matthew Garrett
2007-07-16 17:06             ` 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 [this message]
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=20070718162510.GA22975@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hughsient@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox