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: Sun, 19 Jun 2022 15:33:30 +0000 [thread overview]
Message-ID: <bug-172421-2300-DcbiQdZKYp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-172421-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=172421
--- Comment #22 from Elmar Stellnberger (estellnb@elstel.org) ---
The patch was not accepted because someone claimed it could damage the
hardware. All lies. As years have gone by these graphics cards are still under
daily use with this UHD patch and no damages have ever occured. As this
hardware is still in use I would really like to see this in mainline, not just
the Mageia kernel. Someone who knows about it, told it would be highly
improbable that this could be detrimental for the hardware. The only fallacy
would be that the screen shows black on a too high TMDS and nobody would ever
continue to run the graphics card with a TMDS that yields a black screen. This
hardware is near to getting phased out on many computers by now and I´d regard
it as ridiculous if the patch is withheld because of the argument that it could
damage hardware on the long run. This hardware will get phased out long before
any damage could ever occur.
As distributors and kernel developers still support Pentium IV hardware I am
reopening this bug. This is about Core 2 aged hardware which is totally
sufficient for UHD/desktop computers. I would never give up my Xi3650 machines
because they are ultimately silent, something you don´t get with a newer
computer. And unfortunately the Xi3650 does not work with newer 3D gaming UHD
graphics cards (these cards inhibt s2ram also on Windows, which isn´t what you
want for a desktop system)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-06-19 15:33 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 [this message]
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-DcbiQdZKYp@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 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).