[Bug 1424] Font rendering glitches with Render Acceleration enabled
on radeon
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Nov 2 08:51:39 PST 2004
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1424
mhopf at suse.de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |eich at pdx.freedesktop.org,
| |xorg-bugzilla-
| |noise at freedesktop.org
Status|NEW |ASSIGNED
------- Additional Comments From mhopf at suse.de 2004-11-02 08:51 -------
Ok, more info (just that so this is not lost):
It seems that the GPU does not fetch the new texture but uses its texture cache
until a sufficiently large (whatever that is) primitive is rendered.
I added a texture buffer ring so that no consecutive textures are stored into
the same part of the video memory - with no effect.
I increased the minimum loaded texture size to 64x64 - with no effect.
I increased the minimum *drawn* texture to 64x8 -> everything looks all right!
Unfortunately, this is no solution, as the render system just has to be able to
draw smaller parts of the texture. E.g. if I fix it for scrolling up (which I
did by adding transparent lines below the current texture), I cannot use the
same texture for scrolling down. And even if I fix both, it is possible that
only a small span of the middle of the texture has to be rendered.
Two possible sollutions:
a) There must be some command like 'fetch the texture. do it now.'
b) For small textures draw a large version into a off-screen frame buffer before
using it. This may sound horribly complicated or slow, but it shouldn't be.
However, the size of the texture that has to be drawn is some magic constant..
--
Configure bugmail: https://freedesktop.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.
More information about the xorg-bugzilla-noise
mailing list