<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Radeon: evergreen Atombios in loop during initialization on ppc64"
href="https://bugs.freedesktop.org/show_bug.cgi?id=59982#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Radeon: evergreen Atombios in loop during initialization on ppc64"
href="https://bugs.freedesktop.org/show_bug.cgi?id=59982">bug 59982</a>
from <span class="vcard"><a class="email" href="mailto:agd5f@yahoo.com" title="Alex Deucher <agd5f@yahoo.com>"> <span class="fn">Alex Deucher</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=59982#c15">comment #15</a>)
<span class="quote">> 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?</span >
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.
<span class="quote">>
> Is there anyway to dump the adapter to determine its state when we hit the
> timeout?</span >
You can dump the mmio registers.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>