From: Stelian Pop <stelian@popies.net>
To: Matthew Garrett <mgarrett@chiark.greenend.org.uk>
Cc: linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: [PATCH, new ACPI driver] new sony_acpi driver
Date: Mon, 14 Feb 2005 11:58:37 +0100 [thread overview]
Message-ID: <20050214105837.GE3233@crusoe.alcove-fr> (raw)
In-Reply-To: <E1D0dqo-00041G-00@chiark.greenend.org.uk>
On Mon, Feb 14, 2005 at 10:53:10AM +0000, Matthew Garrett wrote:
> Stelian Pop <stelian@popies.net> wrote:
>
> > Privately I've had many positive feedbacks from users of this driver
> > (and no negative feedback), including Linux distributions who wish
> > to include it into their kernels. The reports are increasing in number,
> > it would seem that newer Sony Vaios are more and more incompatible
> > with sonypi and require sony_acpi to control the screen brightness.
>
> The sonypi driver seems to be necessary to catch Vaio hotkey events,
> including the sleep button. I've checked a couple of DSDTs, and it seems
> that the more recent Vaios are lacking the SPIC entries but still don't
> have the sleep button defined. Is there any chance of this driver being
> able to catch hotkey events?
I don't believe so.
> Related to that, I have a nastyish hack which lets the sonypi driver
> generate ACPI events whenever a hotkey is pressed. Despite not strictly
> being ACPI events, this makes it much easier to integrate sonypi stuff
> with general ACPI support. I'll send it if you're interested.
Wouldn't be more useful to make the ACPI hotkeys generate an
input event (like sonypi does) and integrate all this at the input
level ?
Stelian.
--
Stelian Pop <stelian@popies.net>
next prev parent reply other threads:[~2005-02-14 10:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 16:18 Stelian Pop
2005-02-10 19:39 ` [ACPI] " Bruno Ducrot
2005-02-11 9:16 ` Stelian Pop
2005-02-11 10:30 ` Jean Delvare
2005-02-11 11:17 ` Stelian Pop
2005-02-11 11:05 ` Pekka Enberg
2005-02-11 11:36 ` Stelian Pop
2005-02-11 12:02 ` Pekka Enberg
2005-02-12 13:21 ` Jean Delvare
2005-02-14 10:07 ` Stelian Pop
2005-02-14 12:13 ` Jean Delvare
2005-02-14 12:38 ` Stelian Pop
2005-02-14 18:42 ` Jean Delvare
2005-02-16 15:39 ` Stelian Pop
2005-02-18 18:38 ` Jean Delvare
2005-02-16 19:12 ` Emmanuel Fleury
2005-02-14 10:53 ` Matthew Garrett
2005-02-14 10:58 ` Stelian Pop [this message]
2005-02-14 20:32 ` Vojtech Pavlik
2005-02-15 16:14 ` Romano Giannetti
2005-02-16 14:41 ` Stelian Pop
2005-02-16 15:40 ` Romano Giannetti
2005-02-16 23:18 ` [ACPI] " Pavel Machek
2005-02-15 15:30 ` [ACPI] " Len Brown
2005-02-15 15:39 ` Stelian Pop
2005-02-16 19:40 ` Bruno Ducrot
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=20050214105837.GE3233@crusoe.alcove-fr \
--to=stelian@popies.net \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mgarrett@chiark.greenend.org.uk \
/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
all inboxes | Powered by JetHome®