From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93715] [r600g] rendering issues with R600_DEBUG=nosb for all three 'raytrace' variants
Date: Thu, 14 Jan 2016 17:24:02 +0000 [thread overview]
Message-ID: <bug-93715-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 982 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93715
Bug ID: 93715
Summary: [r600g] rendering issues with R600_DEBUG=nosb for all
three 'raytrace' variants
Product: Mesa
Version: git
Hardware: All
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: Dieter@nuetzel-hh.de
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 121038
--> https://bugs.freedesktop.org/attachment.cgi?id=121038&action=edit
vsraytrace.png
It occurs with RV730 and NI/Turks XT.
I've set Hardware to 'All' cause both x86 (IA32) and x86-64 (AMD64) are broken.
'all three 'raytrace' variants' mean:
vsraytrace
fsraytrace
gsraytrace
Have a look at the attachments.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2414 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
next reply other threads:[~2016-01-14 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 17:24 bugzilla-daemon [this message]
2016-01-14 17:24 ` [Bug 93715] [r600g] rendering issues with R600_DEBUG=nosb for all three 'raytrace' variants bugzilla-daemon
2016-01-14 17:25 ` bugzilla-daemon
2016-01-14 17:42 ` bugzilla-daemon
2017-06-22 17:20 ` bugzilla-daemon
2017-06-26 23:55 ` bugzilla-daemon
2019-09-18 19:20 ` 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-93715-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).