All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31578] New: r600g: enforce minimum stride on render target texture images causes texture corruption on teapot demp.
Date: Fri, 12 Nov 2010 04:01:38 -0800 (PST)	[thread overview]
Message-ID: <bug-31578-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: r600g: enforce minimum stride on render target texture
                    images causes texture corruption on teapot demp.
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: lists@andyfurniss.entadsl.com


Running rv670, d-r-t. Tiling on/off doesn't affect.

Mesa demo teapot and openarena has corrupt tectures since -

commit 7fb16423cc325efcdcf6e4954a5ac71d8f96dbf8
Author: Keith Whitwell <keithw@vmware.com>
Date:   Thu Nov 11 16:20:24 2010 +0000

    r600g: enforce minimum stride on render target texture images

    Fixes piglit/fbo_readpixels since staging upload changes.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2010-11-12 12:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 12:01 bugzilla-daemon [this message]
2010-11-15 21:42 ` [Bug 31578] r600g: enforce minimum stride on render target texture images causes texture corruption on teapot demp bugzilla-daemon
2010-11-15 23:48 ` bugzilla-daemon
2010-11-18  8:06 ` bugzilla-daemon
2010-11-18 12:36 ` 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-31578-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.