[Bug 33867] [bisected] Graphics corruption related to pageflip ioctl support in 2.6.38-rc*
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Feb 3 01:56:35 PST 2011
https://bugs.freedesktop.org/show_bug.cgi?id=33867
--- Comment #1 from Dave Witbrodt <dawitbro at sbcglobal.net> 2011-02-03 01:56:35 PST ---
I would also like to mention that, other than the 'prboom-plus' all-black melt
glitch, everything is working fine. Even 'torcs', which has given me a great
deal of problems in the past when testing cutting-edge drivers/software, runs
better than I've ever seen it (since I used the 'nvidia' blob with my long-dead
GeForce 7950GT. I have never been able to play the "Forza" track in 'torcs'
with an open source driver -- the frame rate was 8 fps or below -- until now.
Other tracks are mostly playable, though their frame rate was capped at 30 fps
or less ever since vline was added to xf86-video-ati; now those rates are 25-35
fps minimum, and frequently reach the 50's (even 60's occasionally).
So, I only discovered the issue with the hangs because I was trying to bisect a
minor glitch. Someone is really doing something right with the open source
support, because just since the last week of January the performance I'm seeing
on this HD 5750 seems 50-150% faster! I don't know what caused it: I have
built newer versions of the kernel, xf86-video-ati, xorg-server, and mesa
during that time. Maybe this has something to do with it:
commit 8c631cfeae29b5236928f759e222aa35e6e4984c
Author: Marek Olšák <maraeo at gmail.com>
Date: Fri Jan 28 22:04:09 2011 +0100
r600g: rework vertex buffer uploads
Only upload the [min_index, max_index] range instead of [0, userbuf_size].
This an important optimization.
Framerate in Lightsmark:
Before: 22 fps
After: 75 fps
The same optimization is already in r300g.
Whoever is actually to blame, I would just like to thank all of you who are
working on this stuff!
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the dri-devel
mailing list