dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 172421] New: radeon: allow to set the TMDS frequency by a special kernel parameter
Date: Wed, 21 Sep 2016 18:15:16 +0000	[thread overview]
Message-ID: <bug-172421-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=172421

            Bug ID: 172421
           Summary: radeon: allow to set the TMDS frequency by a special
                    kernel parameter
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.8.0-rc7+
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: enhancement
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: estellnb@elstel.org
        Regression: No

Despite different claims by ATI in 2016 Radeon R5 230 graphics cards featuring
HDMI, DVI and VGA had originally been sold as 4K-ready up to the year 2015. The
only prove I have for this is a comercial invoice from Nexus Mobile and a
packaging card. As far as I know Radeon R5 230 cards currently sold can still
be run stable and reliable under UltraHD provided that you apply the right
kernel patch (see for the attachement). Unfortunately neither my former
merchant nor ATI have responded about my questions concerning this change in
trade and marketing policy.

  My request would now be to integrate the provided patch into the mainline
kernel. It does not change the behaviour of the radeon driver unless you
specify a nonzero value for the radeon.hdmimhz parameter. If you do I have
tested the R5 230 cards I have to run stable and reliably for days. At least
the 2GB variant of this card has largely sufficient resources for proficient
desktop computing under UltraHD including image manipulation in 3840x2160.

  While never officially discussed for the radeon driver nouveau is already
implementing a similar parameter called nouveau.hdmimhz since kernel 4.5.x.
Though it thereby becomes possible to specify a hdmimhz that is far above the
cards technical possibilties the nouveau developers I have talked with say that
it would rarely be possible to damage any card by overcloking the TMDS. In deed
I have successfully been overclocking my GeForce 9600M GT to feature 4K/2160p. 

  Even specifying values considerable higher than 225MHz did not damage my
GeForce 9600M GT though the screen stayed black upon the nouveau driver
initialization. While the Radeon R5 230 works well at 297MHz (as long as you
specify that via radeon.hdmimhz) I have similarly to the GeForce 9600M GT tried
to overclock a Radeon R7 240. It did produce stable images at a higher hdmimhz
like 330 though the HDMI input of my monitor features no more than 30Hz at
3840x2160 (tested with or without a DP-adapter).

  While it remains questionable if the provided patch can improve things for
newer Radeon cards I would believe it to be beneficial for some elder cards. At
least it is known to be beneficial for the R5 230 initially marketed as
4K-ready. The according radeon patch provided with this report has so far
already been accepted by the Mageia 6 distribution. Though the attached patch
is for application at the current 4.8.0-rcX+ kernels most of my machines that
rely on it still run with 4.6.0.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2016-09-21 18:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 18:15 bugzilla-daemon [this message]
2016-09-21 18:16 ` [Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter bugzilla-daemon
2016-09-21 18:17 ` bugzilla-daemon
2016-09-21 18:30 ` bugzilla-daemon
2016-09-21 18:37 ` bugzilla-daemon
2016-09-21 18:38 ` bugzilla-daemon
2016-09-21 18:49 ` bugzilla-daemon
2016-09-21 19:59 ` bugzilla-daemon
2016-09-21 20:16 ` bugzilla-daemon
2016-09-21 20:20 ` bugzilla-daemon
2016-09-22  7:07 ` bugzilla-daemon
2016-09-22  7:24 ` bugzilla-daemon
2016-09-22 13:51 ` bugzilla-daemon
2016-09-23  2:53 ` bugzilla-daemon
2016-09-23  7:36 ` bugzilla-daemon
2016-09-23 16:22 ` bugzilla-daemon
2016-09-23 17:27 ` bugzilla-daemon
2016-09-24 18:08 ` bugzilla-daemon
2017-12-16 18:52 ` bugzilla-daemon
2018-11-27  3:33 ` bugzilla-daemon
2018-11-27 12:28 ` bugzilla-daemon
2019-02-23 12:44 ` bugzilla-daemon
2022-06-19 15:33 ` bugzilla-daemon
2022-06-19 15:43 ` bugzilla-daemon
2023-01-03 12:16 ` bugzilla-daemon
2023-04-04  8:21 ` 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-172421-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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).