From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101594] Blender doesn't detect OpenCL with Clover
Date: Mon, 21 Aug 2017 22:54:28 +0000 [thread overview]
Message-ID: <bug-101594-502-7wrWlU2FAW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101594-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 804 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101594
Jan Vesely <jan.vesely@rutgers.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOTABUG
Status|NEW |RESOLVED
--- Comment #3 from Jan Vesely <jan.vesely@rutgers.edu> ---
Blender uses whitelist of supported platform, clover is not a supported
platform.
if you run:
blender --debug-cycles
you should see message(s) like:
"Ignoring device ..., not officially supported yet"
running:
CYCLES_OPENCL_SPLIT_KERNEL_TEST=1 blender
will make clover devices visible to blender
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2298 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-08-21 22:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 10:05 [Bug 101594] Blender doesn't detect OpenCL with Clover bugzilla-daemon
2017-06-27 16:34 ` bugzilla-daemon
2017-06-27 23:24 ` bugzilla-daemon
2017-07-28 3:22 ` bugzilla-daemon
2017-08-21 22:54 ` bugzilla-daemon [this message]
2017-09-10 9:24 ` bugzilla-daemon
2017-09-10 16:33 ` bugzilla-daemon
2017-09-10 18:17 ` bugzilla-daemon
2017-09-10 23:28 ` 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-101594-502-7wrWlU2FAW@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