From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Add some hooks to generic suspend code
Date: Wed, 01 Jun 2005 18:34:17 +1000 [thread overview]
Message-ID: <1117614857.19020.32.camel@gaston> (raw)
In-Reply-To: <20050601081336.GA6693@elf.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]
On Wed, 2005-06-01 at 10:13 +0200, Pavel Machek wrote:
> Hi!
>
> > > Why do you need it? Do you initiate suspend without userland asking
> > > you to?
> >
> > Because there is an existing API, via /dev/apm_bios, and that's all X
> > understands ! And because I've always done that ;)
>
> Try stopping doing that ;-).
Certainly not short-term. Again, it would be nice to have something
better, but heh, you need to go step by step. I have this big rework
where I re-implement most of the pmac suspend code on top of the generic
code (cleans up a lot of stuff) but I don't want to touch the userland
ABI for now, that would be too much of a chance. And /dev/apm_bios X
notofication stuff seems to actually fix problems for some users.
> [On i386, we do not emulate apm, and it still works. Reason is that we
> switch to other console before suspend, so X has to give up
> framebuffer control, anyway.]
Well, I sort-of work :) I have reported cases of X locking the machine
up under some circumstances. Note that historically, I was not switching
consoles in the pmac PM code, though I'm doing it nowadays.
There are other uses of those "events" in /dev/apm_bios. Some people run
scripts on resume triggered by these for example, etc...
I'd rather not break an existing and relied upon userland interface now,
at least not until we have a well accepted replacement that has been
around for some time.
I do agree however that it may be nice to make the APM emulation code
more generic & shared between architectures. That's something I intend
to look into next. But I would like my current stuff to get in after
2.6.12 is released.
Ben.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux-pm mailing list <linux-pm@lists.osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] [RFC] Add some hooks to generic suspend code
Date: Wed, 01 Jun 2005 18:34:17 +1000 [thread overview]
Message-ID: <1117614857.19020.32.camel@gaston> (raw)
In-Reply-To: <20050601081336.GA6693@elf.ucw.cz>
On Wed, 2005-06-01 at 10:13 +0200, Pavel Machek wrote:
> Hi!
>
> > > Why do you need it? Do you initiate suspend without userland asking
> > > you to?
> >
> > Because there is an existing API, via /dev/apm_bios, and that's all X
> > understands ! And because I've always done that ;)
>
> Try stopping doing that ;-).
Certainly not short-term. Again, it would be nice to have something
better, but heh, you need to go step by step. I have this big rework
where I re-implement most of the pmac suspend code on top of the generic
code (cleans up a lot of stuff) but I don't want to touch the userland
ABI for now, that would be too much of a chance. And /dev/apm_bios X
notofication stuff seems to actually fix problems for some users.
> [On i386, we do not emulate apm, and it still works. Reason is that we
> switch to other console before suspend, so X has to give up
> framebuffer control, anyway.]
Well, I sort-of work :) I have reported cases of X locking the machine
up under some circumstances. Note that historically, I was not switching
consoles in the pmac PM code, though I'm doing it nowadays.
There are other uses of those "events" in /dev/apm_bios. Some people run
scripts on resume triggered by these for example, etc...
I'd rather not break an existing and relied upon userland interface now,
at least not until we have a well accepted replacement that has been
around for some time.
I do agree however that it may be nice to make the APM emulation code
more generic & shared between architectures. That's something I intend
to look into next. But I would like my current stuff to get in after
2.6.12 is released.
Ben.
next prev parent reply other threads:[~2005-06-01 8:34 UTC|newest]
Thread overview: 24+ 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 7:29 ` Benjamin Herrenschmidt
2005-05-31 10:13 ` [linux-pm] " Pavel Machek
2005-05-31 14:44 ` Benjamin Herrenschmidt
2005-05-31 14:44 ` [linux-pm] " Benjamin Herrenschmidt
2005-05-31 21:25 ` Pavel Machek
2005-05-31 21:25 ` [linux-pm] " Pavel Machek
2005-05-31 23:31 ` Benjamin Herrenschmidt
2005-05-31 23:31 ` [linux-pm] " Benjamin Herrenschmidt
2005-06-01 8:13 ` Pavel Machek
2005-06-01 8:13 ` [linux-pm] " Pavel Machek
2005-06-01 8:34 ` Benjamin Herrenschmidt [this message]
2005-06-01 8:34 ` Benjamin Herrenschmidt
2005-06-01 9:06 ` Pavel Machek
2005-06-01 9:06 ` [linux-pm] " Pavel Machek
2005-06-01 9:36 ` Nigel Cunningham
2005-06-01 9:36 ` [linux-pm] " Nigel Cunningham
2005-06-01 9:55 ` Pavel Machek
2005-06-01 9:55 ` [linux-pm] " Pavel Machek
2005-06-01 10:38 ` Benjamin Herrenschmidt
2005-06-01 10:38 ` [linux-pm] " Benjamin Herrenschmidt
2005-06-02 16:21 ` Stefan Seyfried
2005-06-02 22:18 ` Benjamin Herrenschmidt
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=1117614857.19020.32.camel@gaston \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.