All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100577] DC + TearFree  display lock
Date: Wed, 05 Jul 2017 18:59:11 +0000	[thread overview]
Message-ID: <bug-100577-502-ASQ39fGA88@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100577-502@http.bugs.freedesktop.org/>


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

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

--- Comment #10 from Andy Furniss <adf.lists@gmail.com> ---
(In reply to Andy Furniss from comment #9)

> One nit I notice is I may not be comparing like with like as current and
> some older 4.11s I still have around all seem to peg memory clock high. 3.7s

Ugh, not 3.7s, I mean amd-staging-4.9s didn't peg memclk high. I don't still
have all the 4.11s I've ever built so don't know when this started for them.

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

[-- Attachment #1.2: Type: text/html, Size: 1366 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

  parent reply	other threads:[~2017-07-05 18:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 10:52 [Bug 100577] DC + TearFree display lock bugzilla-daemon
2017-04-06  2:29 ` bugzilla-daemon
2017-05-04  9:08 ` bugzilla-daemon
2017-05-04  9:10 ` bugzilla-daemon
2017-05-06 17:54 ` bugzilla-daemon
2017-05-07  7:38 ` bugzilla-daemon
2017-05-16 21:47 ` bugzilla-daemon
2017-05-17 13:16 ` bugzilla-daemon
2017-05-17 22:17 ` bugzilla-daemon
2017-07-05 18:44 ` bugzilla-daemon
2017-07-05 18:59 ` bugzilla-daemon [this message]
2017-07-05 19:19 ` bugzilla-daemon
2017-07-05 20:01 ` bugzilla-daemon
2017-07-05 20:02 ` bugzilla-daemon
2017-07-05 20:03 ` bugzilla-daemon
2017-07-05 20:11 ` bugzilla-daemon
2017-07-05 20:37 ` bugzilla-daemon
2017-08-16 12:54 ` 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-100577-502-ASQ39fGA88@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.