On 9/17/07, Keith Whitwell <[EMAIL PROTECTED]> wrote:
>
> I've been thinking about this a little more and wonder if we can get
> away with slightly relaxed semantics compared to NO_MOVE in some cases
> at least.
>
> In the current SWZ branch, we're pre-validating one or two buffers (VB,
> indirect
I'm just looking at the list handling code in the TTM for libdrm,
and I really don't think we can just leave it as-is but making it generic
also doesn't look that easy (it would at least require adding destructor
paths for free list object contents)
Thomas, any ideas on how best to handle it?
http://bugs.freedesktop.org/show_bug.cgi?id=12444
--- Comment #11 from [EMAIL PROTECTED] 2007-09-20 20:58 PST ---
Can you try again with ati git master? I want to make sure I've fixed this for
real.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
---
http://bugs.freedesktop.org/show_bug.cgi?id=11434
--- Comment #15 from [EMAIL PROTECTED] 2007-09-20 11:49 PST ---
(In reply to comment #11)
> same fail on gutsy
> xserver-xorg-video-ati version: 6.6.193
>
I have no bug with 6.7.193 ! great work
thanks
--
Configure bugmail: http:
http://bugs.freedesktop.org/show_bug.cgi?id=12502
--- Comment #2 from [EMAIL PROTECTED] 2007-09-20 11:47 PST ---
Created an attachment (id=11662)
--> (http://bugs.freedesktop.org/attachment.cgi?id=11662&action=view)
Warcraft with missing-text corruption
--
Configure bugmail: http:
http://bugs.freedesktop.org/show_bug.cgi?id=12502
--- Comment #1 from [EMAIL PROTECTED] 2007-09-20 11:46 PST ---
Created an attachment (id=11661)
--> (http://bugs.freedesktop.org/attachment.cgi?id=11661&action=view)
Warcraft with stretched-text corruption.
--
Configure bugmail: ht
http://bugs.freedesktop.org/show_bug.cgi?id=12502
Summary: Corrupt text in World of Warcraft when VBOs are enabled.
Product: Mesa
Version: CVS
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
http://bugs.freedesktop.org/show_bug.cgi?id=12444
--- Comment #10 from [EMAIL PROTECTED] 2007-09-20 06:26 PST ---
(In reply to comment #9)
> Yes, it worked! :) Thank you very much!
>
> Do I leave this bug open or do you close it when it is fixed proper?
>
leave it open for now. I
