<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - radeon: allow the user to set a maximum HDMI pixel clock (in MHz) by a kernel parameter"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93885#c20">Comment # 20</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - radeon: allow the user to set a maximum HDMI pixel clock (in MHz) by a kernel parameter"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93885">bug 93885</a>
from <span class="vcard"><a class="email" href="mailto:estellnb@elstel.org" title="Elmar Stellnberger <estellnb@elstel.org>"> <span class="fn">Elmar Stellnberger</span></a>
</span></b>
<pre>Great! Stunning! Now that has worked right from the start. A little change to
radeon_dvi_mode_valid and radeon_dig_monitor_is_duallink was fully sufficient
to achieve 3840x2160@30 - and the mode is offered automatically by a mhz of
297.
Many thanks for hinting me, Alex! I wouldn`t have found it entirely on my own.
Are there any chances to get a well prepared patch for the radeon.hdmimhz
parameter into the final 4.5.0 release?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>