http://bugzilla.suse.com/show_bug.cgi?id=1120414 http://bugzilla.suse.com/show_bug.cgi?id=1120414#c12 --- Comment #12 from Takashi Iwai --- (In reply to Elmar Stellnberger from comment #11)

No, I donŽt really understand that. If someone uses the radeon.hdmimhz parameter he will for sure tell you in a bug report or a support request. You do not need to offer support for it though I believe that there is little difference between a setting with natural and overclocked TMDS if overclocking works (without blackscreening). To my experience overclocking the TMDS either causes a black screen or it will naturally cause all default graphics modes to be recognized that are possible under a specific TMDS frequency. Besides this I have written a nice article at https://www.elstel.org/software/hunt-for-4K-UHD-2160p.html.en which tells you how to configure non-default graphics modes.

Taking the patch means that we are responsible for it as distributor, and if it's risky, that's a big question to us. A module option isn't a perfect protection at all, either; you can boot simply by typing it on GRUB menu. It may toast something before asking user to proceed / confirm the risk. If this is absolutely safe and useful, it should be still able to convince upstream. That's the best way to go, after all. Discussing details here won't help much, unfortunately. And, please avoid spreading FUD about AMD developers; they refused such a change not because they want to sell the newer boards. If it's about driver's hardware spec, one must be absolutely sure. With an upstream hat on, I can understand this attitude quite well. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.