From: Pavel Machek <pavel@suse.cz>
To: Oliver Neukum <oliver@neukum.org>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
Richard Purdie <rpurdie@rpsys.net>,
James Simmons <jsimmons@pentafluge.infradead.org>,
Adrian Bunk <bunk@stusta.de>,
Linux Input Devices <linux-input@atrey.karlin.mff.cuni.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dmitry.torokhov@gmail.com
Subject: Re: 2.6: drivers/input/power.c is never built
Date: Fri, 18 Feb 2005 21:14:30 +0100 [thread overview]
Message-ID: <20050218201429.GA1403@elf.ucw.cz> (raw)
In-Reply-To: <200502181805.13129.oliver@neukum.org>
Hi!
> > > Yes, there are. They can probably stay... Or we can get "battery low"
> > > key.
> >
> > We even have an event class for that, EV_PWR in the input subsystem.
>
> Over that route we'd arrive at a situation where power management
> without the input layer is impossible. Think about embedded stuff I wonder
> whether this is viable.
I'd say it is: you need some support to get it into userspace. And I'd
certianly prefer input infrastructure over ACPI infrastructure...
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-18 20:15 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 0:47 2.6: drivers/input/power.c is never built Adrian Bunk
2005-02-14 18:04 ` James Simmons
2005-02-14 19:34 ` Vojtech Pavlik
2005-02-18 12:22 ` Pavel Machek
2005-02-18 13:10 ` Richard Purdie
2005-02-18 13:26 ` Pavel Machek
2005-02-18 13:36 ` Oliver Neukum
2005-02-18 16:01 ` Pavel Machek
2005-02-18 17:00 ` Vojtech Pavlik
2005-02-18 17:05 ` Oliver Neukum
2005-02-18 17:48 ` Vojtech Pavlik
2005-02-18 21:32 ` James Simmons
2005-02-18 20:14 ` Pavel Machek [this message]
2005-02-18 20:39 ` Oliver Neukum
2005-02-18 18:19 ` Dmitry Torokhov
2005-02-18 18:39 ` Vojtech Pavlik
2005-02-18 19:20 ` Dmitry Torokhov
2005-02-18 20:05 ` Vojtech Pavlik
2005-02-18 20:24 ` Pavel Machek
2005-02-18 20:40 ` Vojtech Pavlik
2005-02-18 20:59 ` Pavel Machek
2005-02-18 21:23 ` Oliver Neukum
2005-02-18 21:34 ` Pavel Machek
2005-02-18 22:00 ` Oliver Neukum
2005-02-18 23:34 ` Pavel Machek
2005-02-18 23:51 ` Oliver Neukum
2005-02-19 0:13 ` Pavel Machek
2005-02-19 1:16 ` Xavier Bestel
2005-02-18 21:38 ` Vojtech Pavlik
2005-02-18 23:31 ` Pavel Machek
2005-02-19 2:58 ` Dmitry Torokhov
2005-02-19 6:28 ` Nigel Cunningham
2005-02-19 6:53 ` Dmitry Torokhov
2005-02-19 9:10 ` Nigel Cunningham
2005-02-21 18:11 ` James Simmons
2005-02-21 18:34 ` Wichert Akkerman
2005-02-21 21:37 ` James Simmons
2005-02-21 22:50 ` Nigel Cunningham
2005-02-21 22:52 ` James Simmons
2005-02-21 22:57 ` Wichert Akkerman
2005-02-21 22:54 ` Wichert Akkerman
2005-02-19 20:29 ` Pavel Machek
2005-02-19 20:31 ` Pavel Machek
2005-02-21 18:19 ` James Simmons
2005-02-18 14:02 ` Richard Purdie
2005-02-18 14:12 ` Dmitry Torokhov
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=20050218201429.GA1403@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=bunk@stusta.de \
--cc=dmitry.torokhov@gmail.com \
--cc=jsimmons@pentafluge.infradead.org \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=rpurdie@rpsys.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