From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Luca <kronos@kronoz.cjb.net>, linux-kernel@vger.kernel.org
Subject: Re: Suspend to RAM: help with whitelist wanted
Date: Sat, 28 Jan 2006 01:31:11 +0000 [thread overview]
Message-ID: <20060128013111.GA30225@srcf.ucam.org> (raw)
In-Reply-To: <20060127232207.GB1617@elf.ucw.cz>
On Sat, Jan 28, 2006 at 12:22:07AM +0100, Pavel Machek wrote:
> If vbetool's primary purpose is to fix video after suspend/resume,
> then perhaps right thing to do is to integrate it into s2ram and
> maintain it there.
That's the primary purpose, though there's a couple of edge cases.
For VBE state saving/restoring, it seems to be important to save the
state before X has started rather than doing so at suspend time - some
i855 systems break otherwise.
Not strictly related - Pavel, try taking a look at the acpi-support
package in http://archive.ubuntu.com/ubuntu/pool/main/a/acpi-support/ .
There's a large list of witelisted hardware there. OSDL recently set up
a mailing list (desktop-portables@lists.osdl.org) for cross-distribution
laptop discussion. It would probably be helpful to discuss working
machines there, rather than duplicate the whitelisting efforts.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2006-01-28 1:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 21:36 Suspend to RAM: help with whitelist wanted Pavel Machek
2006-01-27 17:04 ` Luca
2006-01-27 23:05 ` Pavel Machek
2006-01-28 1:05 ` Olivier Galibert
2006-01-28 8:12 ` Pavel Machek
2006-01-27 23:22 ` Pavel Machek
2006-01-28 1:31 ` Matthew Garrett [this message]
2006-01-28 8:42 ` Pavel Machek
2006-01-29 7:12 ` Matthew Garrett
2006-02-04 21:11 ` Pavel Machek
2006-01-28 15:58 ` Luca
2006-01-28 16:04 ` Jan De Luyck
2006-01-28 17:11 ` Luca
2006-01-28 16:27 ` Pavel Machek
2006-01-28 16:36 ` Pavel Machek
2006-01-29 14:42 ` Luca
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=20060128013111.GA30225@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=kronos@kronoz.cjb.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).