All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 59982] Radeon: evergreen Atombios in loop during initialization on ppc64
Date: Fri, 22 Feb 2013 12:52:32 +0000	[thread overview]
Message-ID: <bug-59982-502-IQ2bK3PjlB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-59982-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1739 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=59982

Lucas Kannebley Tavares <lucaskt@linux.vnet.ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #75196|0                           |1
        is obsolete|                            |

--- Comment #23 from Lucas Kannebley Tavares <lucaskt@linux.vnet.ibm.com> ---
Created attachment 75313
  --> https://bugs.freedesktop.org/attachment.cgi?id=75313&action=edit
Fixes on the Workaround

Hi Jerome, this is the patch I actually used.
I had already done what you said and also removed a couple of left shifts you
had added upon reading the low words.
The results are still the same, though.

Right now I'm tracing it by going through the code between the call to
DAC1OutputControl on radeon_atom_encoder_dpms_avivo and the call to
DPEncoderService on either radeon_dp_encoder_service or radeon_dp_link_train
and instrumenting it, not sure which one yet, but I'm guessing the first. This
is to make sure the driver is not doing anything else that could be going wrong
in between calls, because after that DAC1OutputControl call, everything is
still fine, it's somewhere in between those calls that the adapter goes to
hell.

Another thing that I'd like to ask is, you suggested me to "make sure the pipes
are off". I've looked through the registers looking for something to get DAC
state or disable them, and have not found it. As far as I can tell, your patch
would already make sure we're not doing improper access, but are there any more
interesting registers I should be looking into as well?

Thanks

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3336 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2013-02-22 12:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 18:37 [Bug 59982] New: Radeon: evergreen Atombios in loop during initialization on ppc64 bugzilla-daemon
2013-01-28 18:38 ` [Bug 59982] " bugzilla-daemon
2013-01-29  3:45 ` bugzilla-daemon
2013-01-29  3:46 ` bugzilla-daemon
2013-01-29 12:42 ` bugzilla-daemon
2013-01-29 12:50 ` bugzilla-daemon
2013-01-30 19:49 ` bugzilla-daemon
2013-01-31 10:57 ` bugzilla-daemon
2013-01-31 15:12 ` bugzilla-daemon
2013-02-06 17:07 ` bugzilla-daemon
2013-02-06 17:08 ` bugzilla-daemon
2013-02-08 17:17 ` bugzilla-daemon
2013-02-08 17:20 ` bugzilla-daemon
2013-02-09 14:40 ` bugzilla-daemon
2013-02-13 13:38 ` bugzilla-daemon
2013-02-13 14:08 ` bugzilla-daemon
2013-02-18 16:22 ` bugzilla-daemon
2013-02-18 16:29 ` bugzilla-daemon
2013-02-20 14:47 ` bugzilla-daemon
2013-02-20 15:33 ` bugzilla-daemon
2013-02-20 15:34 ` bugzilla-daemon
2013-02-20 16:33 ` bugzilla-daemon
2013-02-20 18:54 ` bugzilla-daemon
2013-02-20 22:03 ` bugzilla-daemon
2013-02-22 12:52 ` bugzilla-daemon [this message]
2013-02-22 15:04 ` bugzilla-daemon
2013-02-27 14:24 ` bugzilla-daemon
2013-02-27 14:26 ` bugzilla-daemon
2013-02-27 15:08 ` bugzilla-daemon
2013-02-27 15:47 ` bugzilla-daemon
2013-02-27 16:29 ` bugzilla-daemon
2013-02-27 17:21 ` bugzilla-daemon
2013-02-27 17:44 ` bugzilla-daemon
2013-02-28 17:34 ` bugzilla-daemon

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=bug-59982-502-IQ2bK3PjlB@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.