dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95206] Display port bandwidth regression
Date: Tue, 10 May 2016 09:27:57 +0000	[thread overview]
Message-ID: <bug-95206-502-T7UlzLWHJX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95206-502@http.bugs.freedesktop.org/>


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

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

--- Comment #8 from Christian L. <barneyman@gmx.de> ---
Hi,

I've bisected the problem down to the following commit to the mainline kernel
(see below). Can I help with some further information?

092c96a8ab9d1bd60ada2ed385cc364ce084180e is the first bad commit
commit 092c96a8ab9d1bd60ada2ed385cc364ce084180e
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Thu Dec 17 10:23:34 2015 -0500

    drm/radeon: fix dp link rate selection (v2)

    Need to properly handle the max link rate in the dpcd.
    This prevents some cases where 5.4 Ghz is selected when
    it shouldn't be.

    v2: simplify logic, add array bounds check

    Reviewed-by: Tom St Denis <tom.stdenis@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

:040000 040000 c27fa6e02534c3ef9f53c3c954fa936b1e414cb3
0be8f64ebe28383efa39ebce68247b148f4a78f2 M    drivers

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

[-- Attachment #1.2: Type: text/html, Size: 1892 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:[~2016-05-10  9:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29 11:40 [Bug 95206] Display port bandwidth regression bugzilla-daemon
2016-04-29 14:19 ` bugzilla-daemon
2016-04-29 14:59 ` bugzilla-daemon
2016-04-29 15:00 ` bugzilla-daemon
2016-04-29 15:01 ` bugzilla-daemon
2016-04-29 15:03 ` bugzilla-daemon
2016-04-29 16:46 ` bugzilla-daemon
2016-04-29 19:51 ` bugzilla-daemon
2016-05-10  9:27 ` bugzilla-daemon [this message]
2016-05-10 20:36 ` bugzilla-daemon
2016-05-11  8:27 ` bugzilla-daemon
2016-05-11 20:22 ` bugzilla-daemon
2016-05-12 11:01 ` bugzilla-daemon
2016-12-08 23:18 ` bugzilla-daemon
2016-12-09 17:16 ` bugzilla-daemon
2016-12-10 16:48 ` bugzilla-daemon
2016-12-10 17:01 ` bugzilla-daemon
2017-01-03  0:53 ` bugzilla-daemon
2017-01-03 15:57 ` bugzilla-daemon
2017-01-03 15:57 ` bugzilla-daemon
2017-01-09  3:40 ` 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-95206-502-T7UlzLWHJX@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