From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 68391] [radeonsi] Crash unigine-sanctuary
Date: Wed, 16 Oct 2013 00:03:41 +0000 [thread overview]
Message-ID: <bug-68391-502-EaXfoB0ekN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-68391-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 346 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=68391
--- Comment #15 from Hohahiu <rakothedin@gmail.com> ---
I tried Unigine-Heaven 3.0 right now. It works fine (a little bit slowly of
course). Which software versions are you using? And I didn't do anything except
s3tc.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1086 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:[~2013-10-16 0:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 17:42 [Bug 68391] New: [radeonsi] Crash unigine-sanctuary bugzilla-daemon
2013-08-21 20:57 ` [Bug 68391] " bugzilla-daemon
2013-08-21 22:16 ` bugzilla-daemon
2013-08-22 3:23 ` bugzilla-daemon
2013-08-23 22:39 ` bugzilla-daemon
2013-08-26 10:47 ` bugzilla-daemon
2013-08-26 11:10 ` bugzilla-daemon
2013-08-29 19:59 ` bugzilla-daemon
2013-08-29 19:59 ` bugzilla-daemon
2013-08-30 14:48 ` bugzilla-daemon
2013-09-21 14:46 ` bugzilla-daemon
2013-10-14 4:07 ` bugzilla-daemon
2013-10-15 3:02 ` bugzilla-daemon
2013-10-15 20:13 ` bugzilla-daemon
2013-10-15 23:08 ` bugzilla-daemon
2013-10-16 0:03 ` bugzilla-daemon [this message]
2013-10-16 19:11 ` bugzilla-daemon
2013-10-17 10:14 ` bugzilla-daemon
2013-10-17 12:41 ` bugzilla-daemon
2013-10-17 15:06 ` bugzilla-daemon
2013-10-18 1:52 ` 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-68391-502-EaXfoB0ekN@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).