All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 30948] New: Regression in r600 driver: due to commit 603741a86df0e43c0b52e8c202a35c7fe2fc1d9c some texture broken
Date: Mon, 18 Oct 2010 03:37:59 -0700 (PDT)	[thread overview]
Message-ID: <bug-30948-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: Regression in r600 driver: due to commit
                    603741a86df0e43c0b52e8c202a35c7fe2fc1d9c some texture
                    broken
           Product: Mesa
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/R600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: crazy-ivanovic@gmx.net


Created an attachment (id=39500)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=39500)
screenshot of breakage due to regression

http://cgit.freedesktop.org/mesa/mesa/commit/?id=603741a86df0e43c0b52e8c202a35c7fe2fc1d9c
does break displaying the wesnoth-gl branch when using the r600 classic driver.
Things are displayed nicely using r600 gallium. It looks like some completely
wrong textures are displayed (so the "wrong stuff" displayed appears to be
something from a wrong region of the grahpics ram or something like this).
Wesnoth is using FBOs (regarding what I heard from alink) to display stuff.

I attached a screenshot of what is shown as well as what should be shown.

To reproduce this:
svn co -r47099 svn://svn.gna.org/svn/wesnoth/branches/ogl wesnoth-ogl
cd wesnoth-ogl
cmake .
make
./wesnoth .

I explicitly mention a revision in case that all the menu setup stuff is
changed over the next days. In general compiling wesnoth can also be done using
scons or autotool and always does require the dependencies listed at
http://wiki.wesnoth.org/CompilingWesnoth . The resulting svn checkout needs
about 1GB on the harddrive and compiling will take some time (usually longer
than compiling a kernel).

-- 
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-10-18 10:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18 10:37 bugzilla-daemon [this message]
2010-10-18 10:38 ` [Bug 30948] Regression in r600 driver: due to commit 603741a86df0e43c0b52e8c202a35c7fe2fc1d9c some texture broken bugzilla-daemon
2011-02-09 15:38 ` [Bug 30948] [RADEON:KMS::R600G] some texture broken regression due to commit 603741a86df0e43c0b52e8c202a35c7fe2fc1d9c bugzilla-daemon
2011-02-13 16:27 ` 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-30948-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.