From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 86663] [radeonsi] Black squares in Sanctum 2
Date: Fri, 28 Nov 2014 13:31:20 +0000 [thread overview]
Message-ID: <bug-86663-502-mvtjvwFioM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-86663-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 580 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=86663
--- Comment #8 from Daniel Scharrer <daniel@constexpr.org> ---
(In reply to Marek Olšák from comment #6)
> The question is how they occur.
Right, any idea how to track that down? I'll try to figure out why glretrace
crashes.
(In reply to Christoph Haag from comment #7)
> Is bug 83510 the same problem?
Looks different enough to me. For example in your videos on that bug the HUD is
alpha-blended just fine over the black spots.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1628 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:[~2014-11-28 13:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 14:38 [Bug 86663] [radeonsi] Black squares in Sanctum 2 bugzilla-daemon
2014-11-24 14:39 ` bugzilla-daemon
2014-11-24 14:39 ` bugzilla-daemon
2014-11-24 14:40 ` bugzilla-daemon
2014-11-24 14:41 ` bugzilla-daemon
2014-11-24 14:55 ` bugzilla-daemon
2014-11-24 15:05 ` bugzilla-daemon
2014-11-26 10:22 ` bugzilla-daemon
2014-11-28 13:09 ` bugzilla-daemon
2014-11-28 13:31 ` bugzilla-daemon [this message]
2014-12-04 21:56 ` bugzilla-daemon
2014-12-12 8:55 ` bugzilla-daemon
2015-01-15 15:18 ` 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-86663-502-mvtjvwFioM@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.