dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66558] RS690: 3D artifacts when playing SuperTuxKart
Date: Wed, 03 Jul 2013 20:15:42 +0000	[thread overview]
Message-ID: <bug-66558-502-nkukPVaMzY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-66558-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 597 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=66558

--- Comment #4 from Björn Beutel <bjoern-beutel@arcor.de> ---
Created attachment 81980
  --> https://bugs.freedesktop.org/attachment.cgi?id=81980&action=edit
Patch that sets the needed CS buffer size in "r300_render_draw_elements"

The attached patch solves the problem for me in Mesa 9.1 and Mesa Git.

For me, it seems as if the buffer is not always properly flushed in between
when "r300_render_draw_elements" has to divide it into two or more runs.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1744 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2013-07-03 20:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 19:53 [Bug 66558] New: RS690: 3D artifacts when playing SuperTuxKart bugzilla-daemon
2013-07-03 19:57 ` [Bug 66558] " bugzilla-daemon
2013-07-03 19:57 ` bugzilla-daemon
2013-07-03 19:59 ` bugzilla-daemon
2013-07-03 19:59 ` bugzilla-daemon
2013-07-03 20:15 ` bugzilla-daemon [this message]
2013-07-03 20:28 ` bugzilla-daemon
2013-07-11  2:39 ` 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=bug-66558-502-nkukPVaMzY@http.bugs.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