https://bugs.freedesktop.org/show_bug.cgi?id=25871
--- Comment #16 from Pierre Ossman pierre-bugzilla@ossman.eu --- (In reply to comment #14)
Thanks for the feedback. So it is a precision issue after all. If fglrx exhibits the same behavior, there is nothing I can do. I don't know of any hardware state which controls precision of texture addressing.
I would guess it needs input from the AMD folks. So I guess getting their attention is one thing that could be done. Maybe a microcode update could solve.
I also haven't tested this in ages. Might not be an issue for modern chips...