From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 74718] r600g: graphics artifacts with geometry shaders with RV730
Date: Wed, 25 Nov 2015 01:54:58 +0000 [thread overview]
Message-ID: <bug-74718-502-Sd9DOSIMla@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-74718-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 622 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=74718
--- Comment #9 from Dieter Nützel <Dieter@nuetzel-hh.de> ---
(In reply to Dieter Nützel from comment #8)
> Is this still a problem for you?
>
> Looks very similar as mesa-demos/glsl/geom-outlining-150 on my RV730 AGP.
> I have a geom-outlining-150-shader.log with R600_DEBUG=gs,vs,fs,ps if needed.
Stays this for you?
'cause my reported 'mesa-demos/glsl/geom-outlining-150' artifacts are SOLVED,
now.
Have a look at:
https://bugs.freedesktop.org/show_bug.cgi?id=83319#c11
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1675 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 prev parent reply other threads:[~2015-11-25 1:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 18:00 [Bug 74718] New: r600g: graphics artifacts with geometry shaders bugzilla-daemon
2014-02-08 18:00 ` [Bug 74718] " bugzilla-daemon
2014-02-08 18:01 ` bugzilla-daemon
2014-02-08 18:01 ` bugzilla-daemon
2014-02-08 18:01 ` bugzilla-daemon
2014-02-08 18:06 ` bugzilla-daemon
2014-02-08 19:48 ` bugzilla-daemon
2014-02-08 19:54 ` [Bug 74718] r600g: graphics artifacts with geometry shaders with RV730 bugzilla-daemon
2014-02-08 20:19 ` bugzilla-daemon
2014-02-08 22:00 ` bugzilla-daemon
2014-10-23 18:51 ` bugzilla-daemon
2015-11-25 1:54 ` bugzilla-daemon [this message]
2016-12-25 10:47 ` 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-74718-502-Sd9DOSIMla@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.