public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mattia Dongili <malattia@linux.it>
To: "Almer S. Tigelaar" <almer@gnome.org>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [PATCH v2.6.29-rc6] sony-laptop.c: Enable special FN key combinations for the Sony VAIO SR model
Date: Sun, 1 Mar 2009 12:53:51 +0900	[thread overview]
Message-ID: <20090301035351.GC24964@kamineko.org> (raw)
In-Reply-To: <1235857044.11958.40.camel@rufio-laptop>

On Sat, Feb 28, 2009 at 10:37:24PM +0100, Almer S. Tigelaar wrote:
> This enables the use of the FN + (F5, F6, F9, F10, F12) keys on newer
> Sony VAIO SR laptops. The patch consists of two (minor) additions: one
> that enables recognition of the FN + F9 key, and another that adds the
> VAIO SR to the list of SNC only models (the SR does not have a SPIC).
> Tested (and working) on my own machine.

Thanks a lot, but a different user already submitted something similar a
few days ago. I'll submit this adnd a few others later.

...
> (Apologies: patch mangled on previous sent, corrected here)
> As a sidenote: This is a rather 'trivial' patch, suitable for back
> porting (to drivers/misc/sony-laptop.c for pre-2.6.29 kernel trees). I
> believe many more of the newer Sony VAIO laptops are SNC only. I added
> only the laptop that I could actually test this for though. Anyhow, this
> 'array of SNC-only exceptions' is going to get longer and longer ... we
> will probably have to come up with some more permanent solution to this.

Yes, I know. I was thinking about just calling the extra acpi method
combinations if all of the SN02, SN03 and SN07 methods are available.
For now all the DSDT I received that have them also required the
additional calls.

-- 
mattia
:wq!

           reply	other threads:[~2009-03-01  3:54 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1235857044.11958.40.camel@rufio-laptop>]

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=20090301035351.GC24964@kamineko.org \
    --to=malattia@linux.it \
    --cc=almer@gnome.org \
    --cc=linux-kernel@vger.kernel.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