From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@zip.com.au>,
Rusty trivial patch monkey Russell <trivial@rustcorp.com.au>,
kernel list <linux-kernel@vger.kernel.org>
Cc: stefandoesinger@gmx.at
Subject: Tips for S3 resume on radeon cards
Date: Fri, 23 Apr 2004 12:23:10 +0200 [thread overview]
Message-ID: <20040423102310.GA8358@elf.ucw.cz> (raw)
Hi!
Stefan has pretty usefull tips for getting S3 to work on radeon
notebooks. This brings whole new class of systems to be usable for S3,
please apply.
Pavel
--- clean/Documentation/power/video.txt 2004-02-05 01:53:53.000000000 +0100
+++ linux/Documentation/power/video.txt 2004-04-23 12:19:00.000000000 +0200
@@ -1,7 +1,7 @@
Video issues with S3 resume
~~~~~~~~~~~~~~~~~~~~~~~~~~~
- 2003, Pavel Machek
+ 2003-2004, Pavel Machek
During S3 resume, hardware needs to be reinitialized. For most
devices, this is easy, and kernel driver knows how to do
@@ -15,7 +15,7 @@
There are three types of systems where video works after S3 resume:
-* systems where video state is preserved over S3. (HP Omnibook xe3)
+* systems where video state is preserved over S3. (Athlon HP Omnibook xe3s)
* systems that initialize video card into vga text mode and where BIOS
works well enough to be able to set video mode. Use
@@ -26,6 +26,10 @@
point, but it happens to work on some machines. Use
acpi_sleep=s3_bios (Athlon64 desktop system)
+* radeon systems, where X can soft-boot your video card. You'll need
+ patched X, and plain text console (no vesafb or radeonfb), see
+ http://www.doesi.gmxhome.de/linux/tm800s3/s3.html. (Acer TM 800)
+
Now, if you pass acpi_sleep=something, and it does not work with your
bios, you'll get hard crash during resume. Be carefull.
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
reply other threads:[~2004-04-23 10:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040423102310.GA8358@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=stefandoesinger@gmx.at \
--cc=trivial@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®