From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31810] New: r600g: Sampling from an alpha texture in a fragment shader
Date: Sun, 21 Nov 2010 04:47:05 -0800 (PST) [thread overview]
Message-ID: <bug-31810-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=31810
Summary: r600g: Sampling from an alpha texture in a fragment
shader
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: otaylor@redhat.com
Created an attachment (id=40447)
--> (https://bugs.freedesktop.org/attachment.cgi?id=40447)
piglit patch described
The attach piglit addition works on g600c and softpipe fails on r600g.
(The test is close to minimal, but not having diagnosed the bug
I don't know if "sampling from an alpha texture" is the fundamental
thing that needs to be tested or not... or there could even be failing
piglit tests elsewhere that are showing the same problem.)
The TGSI looks right:
DCL IN[0], COLOR, LINEAR
DCL IN[1], GENERIC[0], PERSPECTIVE
DCL OUT[0], COLOR
DCL SAMP[0]
DCL TEMP[0]
0: TEX TEMP[0], IN[1], SAMP[0], 2D
1: MUL OUT[0], IN[0], TEMP[0].wwww
2: END
VERT
Despite spending a lot of time fooling around this yesterday and checking
what I thought were the obvious things I really have no idea what is going
on; hopefully it will be obvious for someone more familiar with the R700
shader code.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-11-21 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 12:47 bugzilla-daemon [this message]
2010-11-21 14:53 ` [Bug 31810] r600g: Sampling from an alpha texture in a fragment shader bugzilla-daemon
2010-11-22 5:56 ` bugzilla-daemon
2010-11-22 6:05 ` 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-31810-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.