From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29726] New CRTC ID query breaks Radeon DRM in Zaphod mode
Date: Wed, 27 Oct 2010 19:48:00 -0700 (PDT) [thread overview]
Message-ID: <20101028024801.030C713004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-29726-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=29726
--- Comment #10 from Lucas <lvella@gmail.com> 2010-10-27 19:48:00 PDT ---
(In reply to comment #9)
> should be fixed on master DDX now.
Thank you so much for your commit. The vsync of the proprietary driver was
broken in the second display in new Ubuntu, so I switched to the free driver,
to find it much better than when I last saw it. No way I would go back to
fglrx, but I still could not use the second display (my TV) the way I was used
to (to watch movies, separated displays/screens, vsync on) because of this
bug... I was using big desktop mode until now!
I just tested the driver with the fix, and vsync seemed to work in zaphod mode,
in both screens. DISPLAY=:0.0 is my monitor with 1280x1024 at 60Hz and
DISPLAY=:0.1 is my TV with 1920x1080, also at 60Hz. I played a movie with
mplayer in both screens (gl backend, vsync on) and I could see no visible tear
that was obvious when vsync was off. glxgears is also limited at 60 FPS, as it
should be.
Now I am not sure how to test it without relying on my eye and a movie (I am
satisfied with the result). My test may be unreliable, since I was not able to
shut off vsync in mplayer in a way that I could see the tears I was used to see
with vsync=off in fglrx. Env var vblank_mode=0 shows no artifacts, neither when
running mplayer nor glxgears, although its FPS is not limited at 60 anymore.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2010-10-28 2:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 15:36 [Bug 29726] New: New CRTC ID query breaks Radeon DRM in Zaphod mode bugzilla-daemon
2010-08-21 15:37 ` [Bug 29726] " bugzilla-daemon
2010-08-21 15:45 ` bugzilla-daemon
2010-08-28 14:42 ` bugzilla-daemon
2010-09-18 23:21 ` bugzilla-daemon
2010-10-24 15:31 ` bugzilla-daemon
2010-10-24 15:33 ` bugzilla-daemon
2010-10-24 23:03 ` bugzilla-daemon
2010-10-25 5:09 ` bugzilla-daemon
2010-10-25 9:11 ` bugzilla-daemon
2010-10-28 1:13 ` bugzilla-daemon
2010-10-28 2:48 ` bugzilla-daemon [this message]
2010-10-28 10:25 ` bugzilla-daemon
2011-01-06 23:54 ` 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=20101028024801.030C713004E@annarchy.freedesktop.org \
--to=bugzilla-daemon@freedesktop.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).