linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stuffed Crust <pizza@shaftnet.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-fbdev-devel@lists.sourceforge.net,
	Christian Hoffmann <chrmhoffmann@gmail.com>,
	Andrew Morton <akpm@osdl.org>,
	Christian Hoffmann <Christian.Hoffmann@wallstreetsystems.com>,
	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 09:36:58 -0500	[thread overview]
Message-ID: <20061117143658.GB5158@shaftnet.org> (raw)
In-Reply-To: <1163744220.5940.443.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]

On Fri, Nov 17, 2006 at 05:17:00PM +1100, Benjamin Herrenschmidt wrote:
> > radeonfb is still using its own code for saving and restoring PCI 
> > registers; I'm in the process of fixing it up to use proper PCI
> > subsystem calls.  That will hopefully work better.   
> > 
> > It's possible there's a good reason (other than "nobody's ported it over 
> > yet") that the radeonfb driver is doing it manually, but I don't know 
> > why that would be the case.  
> 
> Well, radeonfb has code to bring back some cards from D2 or D3 cold (or
> hard reset). It differenciates those states by checking if the config
> space has been trashed. We should try to find out some better way.

The d2 vs d3 is determined by chipset in advance -- powermacs and some 
thinkpads use d2, and everyone else uses d3.

On resume, we check that same flag, and restore differently.  We only 
checked the config space on D3 resume, and restored everything if the 
first byte was trashed..   

If I understand what you're saying correctly, if we re-write a valid set
of pci registers, we'll trash the radeon state?   Why _wouldn't_ a D3 
resume be trashed?

 - 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 --]

  reply	other threads:[~2006-11-17 14:36 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                     ` Stuffed Crust [this message]
2006-11-17 21:57                       ` Benjamin Herrenschmidt
2006-11-17  6:07               ` [Linux-fbdev-devel] " Stuffed Crust
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=20061117143658.GB5158@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 \
    /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).