From: Stefan Seyfried <seife@suse.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [RFC] Add some hooks to generic suspend code
Date: Thu, 02 Jun 2005 18:21:49 +0200 [thread overview]
Message-ID: <429F321D.9000009@suse.de> (raw)
In-Reply-To: <20050531212556.GA14968@elf.ucw.cz>
Pavel Machek wrote:
> Anyway, it should not be arch-dependend. We need one good mechanism of
> notifying userland, not one per architecture.
Yes.
>> Sure, ideally. However, existing X knows how to deal with APM events,
>> and thus APM emulation is an important thing to get something that
>> works. Pne thing I should do is consolidate PPC APM emu with ARM one as
>> I think Russell improve my stuff significantly.
>
> Perhaps we need apm emulation on i386, too?
No. This is too ugly for words IMO. If we have one good mechanism of
notifying userland, X can use this mechanism. Let's kill APM, not keep
it alive.
--
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
next prev parent reply other threads:[~2005-06-02 16:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 7:29 [RFC] Add some hooks to generic suspend code Benjamin Herrenschmidt
2005-05-31 10:13 ` [linux-pm] " Pavel Machek
2005-05-31 14:44 ` Benjamin Herrenschmidt
2005-05-31 21:25 ` Pavel Machek
2005-05-31 23:31 ` Benjamin Herrenschmidt
2005-06-01 8:13 ` Pavel Machek
2005-06-01 8:34 ` Benjamin Herrenschmidt
2005-06-01 9:06 ` Pavel Machek
2005-06-01 9:36 ` Nigel Cunningham
2005-06-01 9:55 ` Pavel Machek
2005-06-01 10:38 ` Benjamin Herrenschmidt
2005-06-02 16:21 ` Stefan Seyfried [this message]
2005-06-02 22:18 ` Benjamin Herrenschmidt
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=429F321D.9000009@suse.de \
--to=seife@suse.de \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.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