From: Stuffed Crust <pizza@shaftnet.org>
To: Christian Hoffmann <chrmhoffmann@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-fbdev-devel@lists.sourceforge.net,
Christian Hoffmann <Christian.Hoffmann@wallstreetsystems.com>,
Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>
Subject: Re: [Linux-fbdev-devel] Fwd: [Suspend-devel] resume not working on acer ferrari 4005 with radeonfb enabled
Date: Fri, 17 Nov 2006 01:07:58 -0500 [thread overview]
Message-ID: <20061117060758.GB25413@shaftnet.org> (raw)
In-Reply-To: <200611162317.30880.chrmhoffmann@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
On Thu, Nov 16, 2006 at 11:17:26PM +0100, Christian Hoffmann wrote:
> Ok, I did that and the machine resumes OK. Now I have the impression that
> accessing the rinfo struct here:
Can you try this updated patch?
http://www.shaftnet.org/users/pizza/radeonfb-atom-2.6.19-v7-WIP1.diff
Changes from v6b (which you were using)
* A few PPC-related fixes and other cleanups from BenH
* Rewrote the suspend/resume code to use standard
pci_save_state/pci_restore_state/pci_set_power_state calls instead
of the manual saving and twiddling of PCI registers.
This power management code change is very much of an experiment -- it's
certianly possible there's a good reason to do it manually, but I
suspect it's just because that code is old.
Let me know if this is an improvement.
- Solomon
--
Solomon Peachy pizza at shaftnet dot org
Melbourne, FL ^^ (mail/jabber/gtalk) ^^
Quidquid latine dictum sit, altum viditur. ICQ: 1318344
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-11-17 6:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 22:08 Fwd: [Suspend-devel] resume not working on acer ferrari 4005 with radeonfb enabled Christian Hoffmann
2006-11-13 23:08 ` Rafael J. Wysocki
2006-11-14 18:51 ` Christian Hoffmann
2006-11-14 21:47 ` Christian Hoffmann
2006-11-14 22:07 ` Benjamin Herrenschmidt
2006-11-15 0:54 ` Christian Hoffmann
2006-11-15 1:48 ` Benjamin Herrenschmidt
2006-11-15 10:09 ` Rafael J. Wysocki
2006-11-16 22:17 ` Christian Hoffmann
2006-11-16 22:44 ` Rafael J. Wysocki
2006-11-17 5:27 ` [Linux-fbdev-devel] " Stuffed Crust
2006-11-17 6:17 ` Benjamin Herrenschmidt
2006-11-17 14:36 ` [Linux-fbdev-devel] " Stuffed Crust
2006-11-17 21:57 ` Benjamin Herrenschmidt
2006-11-17 6:07 ` Stuffed Crust [this message]
2006-11-17 15:41 ` Stuffed Crust
2006-11-17 20:33 ` Christian Hoffmann
2006-11-17 21:59 ` Benjamin Herrenschmidt
2006-11-17 22:02 ` [Linux-fbdev-devel] Fwd: [Suspend-devel] resume not working onacer " Christian Hoffmann
2006-11-17 22:34 ` Benjamin Herrenschmidt
2006-11-14 22:36 ` [Linux-fbdev-devel] Fwd: [Suspend-devel] resume not working on acer " Rafael J. Wysocki
2006-11-14 22:56 ` Pavel Machek
2006-11-14 22:57 ` [Linux-fbdev-devel] " Rafael J. Wysocki
2006-11-14 23:12 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-11-10 23:31 Rafael J. Wysocki
2006-11-11 1:49 ` Benjamin Herrenschmidt
2006-11-11 13:45 ` [Linux-fbdev-devel] " Stuffed Crust
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=20061117060758.GB25413@shaftnet.org \
--to=pizza@shaftnet.org \
--cc=Christian.Hoffmann@wallstreetsystems.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=chrmhoffmann@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--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;
as well as URLs for NNTP newsgroup(s).