From: Pavel Machek <pavel@suse.cz>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Stelian Pop <stelian@popies.net>,
Matthew Garrett <mgarrett@chiark.greenend.org.uk>,
linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] Re: [PATCH, new ACPI driver] new sony_acpi driver
Date: Thu, 17 Feb 2005 00:18:12 +0100 [thread overview]
Message-ID: <20050216231812.GA3865@elf.ucw.cz> (raw)
In-Reply-To: <20050214203211.GA8007@ucw.cz>
Hi!
> > > 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 ?
>
> Yes, I'd like to see that. The other possible way is have the input
> layer generate ACPI events for power-related keys.
No; ACPI events are ugly hack. They should die, die, die....
We should probably switch even stuff like acpi power button to input
layer, etc.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2005-02-16 23:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 16:18 [PATCH, new ACPI driver] new sony_acpi driver Stelian Pop
2005-02-11 10:30 ` Jean Delvare
2005-02-11 11:17 ` Stelian Pop
2005-02-14 10:53 ` Matthew Garrett
2005-02-14 10:58 ` Stelian Pop
[not found] ` <20050214105837.GE3233-KwDxFO93HejPHUqn3ntIkQ@public.gmane.org>
2005-02-14 20:32 ` Vojtech Pavlik
[not found] ` <20050214203211.GA8007-+ZI9xUNit7I@public.gmane.org>
2005-02-15 16:14 ` Romano Giannetti
[not found] ` <20050215161412.GC20951-NfIQswJzSEaq9fEpoSJUslHdEuJhDOxL@public.gmane.org>
2005-02-16 14:41 ` Stelian Pop
[not found] ` <20050216144156.GA4372-KwDxFO93HejPHUqn3ntIkQ@public.gmane.org>
2005-02-16 15:40 ` Romano Giannetti
2005-02-16 23:18 ` Pavel Machek [this message]
[not found] ` <20050210161809.GK3493-KwDxFO93HejPHUqn3ntIkQ@public.gmane.org>
2005-02-10 19:39 ` Bruno Ducrot
[not found] ` <20050210193937.GH1145-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-02-11 9:16 ` 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
[not found] ` <20050212142103.5e1a79f9.khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
2005-02-14 10:07 ` Stelian Pop
2005-02-14 12:13 ` Jean Delvare
2005-02-14 12:38 ` Stelian Pop
[not found] ` <20050214123822.GF3233-KwDxFO93HejPHUqn3ntIkQ@public.gmane.org>
2005-02-14 18:42 ` Jean Delvare
[not found] ` <20050214194235.073f5850.khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
2005-02-16 15:39 ` Stelian Pop
[not found] ` <20050216153924.GC4372-KwDxFO93HejPHUqn3ntIkQ@public.gmane.org>
2005-02-18 18:38 ` Jean Delvare
[not found] ` <20050211113636.GI3263-KwDxFO93HejPHUqn3ntIkQ@public.gmane.org>
2005-02-16 19:12 ` Emmanuel Fleury
2005-02-15 15:30 ` Len Brown
2005-02-15 15:39 ` [ACPI] " Stelian Pop
[not found] ` <20050215153912.GA3523-KwDxFO93HejPHUqn3ntIkQ@public.gmane.org>
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=20050216231812.GA3865@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mgarrett@chiark.greenend.org.uk \
--cc=stelian@popies.net \
--cc=vojtech@suse.cz \
/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