All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter
Date: Tue, 03 Jan 2023 12:16:24 +0000	[thread overview]
Message-ID: <bug-172421-2300-PXdyQNK8CV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-172421-2300@https.bugzilla.kernel.org/>

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

Eduard Bloch (blade@debian.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |blade@debian.org

--- Comment #24 from Eduard Bloch (blade@debian.org) ---
Hey guys, I am trying to port this mod to AMDGPU. The intention is, however,
not to unlock the advertised features but to force an APU to accept HDMI clocks
over a DVI port (with DVI-HDMI cable, the monitor expects HDMI signal).

The port itself is easy but it does not work. amdgpu.hdmimhz=... parameter has
apparently no effect, Xorg keeps reporting:

[    16.107] (--) AMDGPU(0): HDMI max TMDS frequency 280000KHz

Does anyone have an idea how to tackle this?

Here is the patch:
https://github.com/Code7R/linux/commits/amdgpu-custom-maxtdmsclock

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2023-01-03 12:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 18:15 [Bug 172421] New: radeon: allow to set the TMDS frequency by a special kernel parameter bugzilla-daemon
2016-09-21 18:16 ` [Bug 172421] " 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 [this message]
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-PXdyQNK8CV@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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 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.