public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Hentges <mailinglisten-H4PcyxPeSRnR7s880joybQ@public.gmane.org>
To: Andrew Barr <barr.156-ZbGKxL/pcrQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Radeon Resuming from S3: Try 2
Date: Thu, 02 Dec 2004 10:59:10 +0100	[thread overview]
Message-ID: <1101981551.20007.7.camel@mhcln03> (raw)
In-Reply-To: <200412012033.05893.barr.156-ZbGKxL/pcrQ@public.gmane.org>

Am Mittwoch, den 01.12.2004, 20:33 -0500 schrieb Andrew Barr:
> Given the recent positive developments and success stories concerning resuming 
> ATI hardware from S3 suspend, I thought I'd give suspending my desktop PC to 
> S3. Briefly, relevant parts of my hardware:

[...]

> It appears I have two options: the s3_late_bios patch 
> or dummydriver/resume-finish-split. What do I need to do to try each one? For 
> example, I know I need to pass acpi_sleep=s3_late_bios to my kernel to use 
> that patch. 

correct

> It's unclear to me what I need to do with the dummydriver or 
> resume-finish-split patches.

Nothing. They don't need any kernel options to work. The dummydriver
only works
for two specific devices identified by their PCI-ID (or whatever you
call that).
It will *not* work for other devices.

You'll have better luck using resume-finish-split as I didn't see
anything device specific in there (well, I didn't look very long heh).

These two patches don't help resuming your Radeon, they just prevent a
freeze during resume caused by *other* devices.

HTH

-- 
Matthias Hentges 
Cologne / Germany

[www.hentges.net] -> PGP welcome, HTML tolerated
ICQ: 97 26 97 4   -> No files, no URL's

My OS: Debian SID. Geek by Nature, Linux by Choice



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  parent reply	other threads:[~2004-12-02  9:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-02  1:33 Radeon Resuming from S3: Try 2 Andrew Barr
     [not found] ` <200412012033.05893.barr.156-ZbGKxL/pcrQ@public.gmane.org>
2004-12-02  9:59   ` Matthias Hentges [this message]
2004-12-02 18:41     ` Andrew Barr

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=1101981551.20007.7.camel@mhcln03 \
    --to=mailinglisten-h4pcyxpesrnr7s880joybq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=barr.156-ZbGKxL/pcrQ@public.gmane.org \
    /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