From: Johannes Berg <johannes@sipsolutions.net>
To: benh@kernel.crashing.org
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
linux-pm <linux-pm@lists.osdl.org>, ralf <ralf@linux-mips.org>
Subject: Re: apm_emulation regression
Date: Thu, 13 Dec 2007 12:40:19 +0100 [thread overview]
Message-ID: <1197546020.6558.247.camel@johannes.berg> (raw)
In-Reply-To: <1197482587.6558.145.camel@johannes.berg>
[-- Attachment #1.1: Type: text/plain, Size: 642 bytes --]
> > That basically means X will break. That's why X broke on the latest
> > ubuntu until I whacked some new scripts in them to force console
> > switching, among other things. Possibly other apps that relied
> > on /dev/apm_bios to be notified of system suspend/resume broke as well.
>
> Ah. I guess I never noticed because I had the scripts to do console
> switching all along.
Actually, it just occurred to me that the *kernel* does a console switch
when we use /sys/power/state, so maybe that is why I never had a problem
rather than userspace doing a console switch (which it only started
doing very recently)
johannes
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
[-- Attachment #2: Type: text/plain, Size: 146 bytes --]
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2007-12-13 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1197427530.8385.59.camel@pasglop>
2007-12-12 18:03 ` apm_emulation regression Johannes Berg
2007-12-13 11:40 ` Johannes Berg [this message]
2007-12-13 20:31 ` Benjamin Herrenschmidt
2007-12-14 0:10 ` Rafael J. Wysocki
2007-12-14 0:04 ` Benjamin Herrenschmidt
2007-12-14 0:05 ` Benjamin Herrenschmidt
2007-12-14 12:18 ` Johannes Berg
2007-12-15 0:20 ` Rafael J. Wysocki
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=1197546020.6558.247.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=benh@kernel.crashing.org \
--cc=linux-pm@lists.osdl.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ralf@linux-mips.org \
--cc=rjw@sisk.pl \
/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