From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82781] Option to disable mclk reclocking with AMD R9 280X (TAHITI) to avoid screen flickering on VGA/CRT
Date: Tue, 19 Aug 2014 17:11:01 +0000 [thread overview]
Message-ID: <bug-82781-2300-tTyKnXJ0YT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-82781-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=82781
--- Comment #9 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Christian Birchinger from comment #7)
> Yes, that patch would indeed fix it in my case.
>
> I was pretty sure i took standard VESA modes and the fact that Windows
> Generic Monitor (no overrides or "hacks" there) values also using the same
> timings tells
> me that they re rather "normal" modes.
>
> i'm going to take your fix and live with it because i prefer when all my
> screen
> modes remain exactly the same between OS switches.
>
> But for curiosity reasons. Do you have a suggestion for mode sources with
> higher
> vblank pauses which are still considered "standard" and not totaly uniq and
> custom? Or might it be possible my 85 Hz value simply has this 450 as
> standard.
>
There's nothing wrong with the modes or non-standard about a mode with a 450 us
vblank time. The issue is it takes 450 us for the mclk to change. It just so
happens that when the vblank period is the same as the switch limit so there is
very little margin for error.
As for tweaking your modeline, you can try adjusting the htotal or vblank_end
parameters. CRT multi-sync monitors are pretty flexible when it comes to
timing.
You can use gtf of cvt to generate vesa compatible modelines. e.g.,
$ gtf 1600 1200 85
# 1600x1200 @ 85.00 Hz (GTF) hsync: 107.10 kHz; pclk: 234.76 MHz
Modeline "1600x1200_85.00" 234.76 1600 1720 1896 2192 1200 1201 1204 1260
-HSync +Vsync
$ cvt 1600 1200 85
# 1600x1200 84.95 Hz (CVT 1.92M3) hsync: 107.21 kHz; pclk: 235.00 MHz
Modeline "1600x1200_85.00" 235.00 1600 1728 1896 2192 1200 1203 1207 1262
-hsync +vsync
your mode:
[ 30.543] (II) RADEON(0): Modeline "1600x1200"x85.0 229.50 1600 1664 1856
2160 1200 1201 1204 1250 +hsync +vsync (106.2 kHz eP)
gtf was the vesa formula used for CRTs and cvt is the newer formula designed
for DFPs. I'm not sure how your modes were generated, but they don't seem to
follow either gtf or cvt. Both the gtf (540 us vblank period) and cvt (558 us
vblank period) modes should work fine as there is pleny of margin.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-08-19 17:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 15:11 [Bug 82781] New: Option to disable mclk reclocking with AMD R9 280X (TAHITI) to avoid screen flickering on VGA/CRT bugzilla-daemon
2014-08-19 15:23 ` [Bug 82781] " bugzilla-daemon
2014-08-19 15:56 ` bugzilla-daemon
2014-08-19 15:57 ` bugzilla-daemon
2014-08-19 16:00 ` bugzilla-daemon
2014-08-19 16:16 ` bugzilla-daemon
2014-08-19 16:27 ` bugzilla-daemon
2014-08-19 16:38 ` bugzilla-daemon
2014-08-19 17:08 ` bugzilla-daemon
2014-08-19 17:11 ` bugzilla-daemon [this message]
2014-08-19 17:58 ` bugzilla-daemon
2014-08-19 18:46 ` bugzilla-daemon
2014-08-19 19:12 ` bugzilla-daemon
2014-08-19 19:39 ` 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-82781-2300-tTyKnXJ0YT@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 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.