From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92936] Tonga powerplay isssues
Date: Thu, 11 Feb 2016 18:36:06 +0000 [thread overview]
Message-ID: <bug-92936-502-CKxD6CUtW8@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92936-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 805 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92936
--- Comment #17 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Andy Furniss from comment #16)
> (In reply to Andy Furniss from comment #13)
> > (In reply to Alex Deucher from comment #12)
> > > Can you try my latest 4.6 wip branch? I fixed it in a more unified way.
> > > http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-4.6-wip
> >
> > This also fixes the memclk getting stuck and uvd corruption issues.
>
> It seems the changes got lost in the latest drm-next-4.6-wip update so I am
> back to stuck mclck.
The fixes went into my drm-fixes branch (drm-fixes-4.5) which will go upstream
for 4.5. My drm-next-4.6-wip branch is just new features for 4.6.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1796 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-02-11 18:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 10:50 [Bug 92936] Tonga powerplay isssues bugzilla-daemon
2015-11-13 15:53 ` bugzilla-daemon
2015-11-13 20:10 ` bugzilla-daemon
2015-11-15 14:29 ` bugzilla-daemon
2015-12-10 12:06 ` bugzilla-daemon
2015-12-12 23:54 ` bugzilla-daemon
2015-12-19 12:16 ` bugzilla-daemon
2015-12-19 12:41 ` bugzilla-daemon
2016-01-25 21:34 ` bugzilla-daemon
2016-02-05 4:13 ` bugzilla-daemon
2016-02-05 10:41 ` bugzilla-daemon
2016-02-05 14:07 ` bugzilla-daemon
2016-02-05 22:24 ` bugzilla-daemon
2016-02-06 22:26 ` bugzilla-daemon
2016-02-08 22:56 ` bugzilla-daemon
2016-02-08 23:01 ` bugzilla-daemon
2016-02-08 23:01 ` bugzilla-daemon
2016-02-11 18:30 ` bugzilla-daemon
2016-02-11 18:36 ` bugzilla-daemon [this message]
2016-02-11 20:07 ` bugzilla-daemon
2016-05-17 10:08 ` bugzilla-daemon
2016-05-17 10:41 ` bugzilla-daemon
2016-05-17 10:42 ` bugzilla-daemon
2016-07-16 14:42 ` bugzilla-daemon
2016-11-07 5:12 ` bugzilla-daemon
2016-11-07 10:17 ` bugzilla-daemon
2018-11-30 17:27 ` 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-92936-502-CKxD6CUtW8@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 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).