From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 59982] Radeon: evergreen Atombios in loop during initialization on ppc64 Date: Mon, 18 Feb 2013 16:29:02 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1953562329==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 5BD0EE63C1 for ; Mon, 18 Feb 2013 08:29:02 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1953562329== Content-Type: multipart/alternative; boundary="1361204942.aF242e1.18039"; charset="us-ascii" --1361204942.aF242e1.18039 Date: Mon, 18 Feb 2013 16:29:02 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=59982 --- Comment #16 from Alex Deucher --- (In reply to comment #15) > Can someone clarify something here? Is the bit that we are waiting to go low > a bit in the adapter's memory? If so, is it the adapter hardware that we are > waiting to set this bit? It's a memory mapped register. We are waiting for one of the display related bits to go low, so it's the GPU that would be setting that bit. The timeout is in the driver. We eventually drop out of the loop in the atom interpretor if we get stuck after a certain number of seconds. > > Is there anyway to dump the adapter to determine its state when we hit the > timeout? You can dump the mmio registers. -- You are receiving this mail because: You are the assignee for the bug. --1361204942.aF242e1.18039 Date: Mon, 18 Feb 2013 16:29:02 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 16 on bug 59982 from 
(In reply to comment #15)
> Can someone clarify something here? Is the bit that we are waiting to go low
> a bit in the adapter's memory? If so, is it the adapter hardware that we are
> waiting to set this bit?

It's a memory mapped register.  We are waiting for one of the display related
bits to go low, so it's the GPU that would be setting that bit.  The timeout is
in the driver.  We eventually drop out of the loop in the atom interpretor if
we get stuck after a certain number of seconds.

> 
> Is there anyway to dump the adapter to determine its state when we hit the
> timeout?

You can dump the mmio registers.

You are receiving this mail because:
  • You are the assignee for the bug.
--1361204942.aF242e1.18039-- --===============1953562329== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1953562329==--