From: ja-cop <ja-cop@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages - Intel OpenCL (NEO)
Date: Fri, 28 Apr 2023 00:05:05 +0200 [thread overview]
Message-ID: <20230427220505.tMnlu6Al5CVpbcMOtHQPTYUS6LeJ5Rn1-xj15jIhq7I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43084@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 686 bytes --]
New comment by ja-cop on void-packages repository
https://github.com/void-linux/void-packages/pull/43084#issuecomment-1526587052
Comment:
Just curious, do you happen to know how this relates to oneAPI and "level zero"? I'd love to use the oneAPI support in Blender for hardware accelerated Cycles, but even after installing `intel-compute-runtime` from this PR, Blender says:
Is this out of scope of this PR? Also, maybe it's because Blender is running in Flatpak? Void's Blender doesn't show the oneAPI tab, I guess it's compiled out or something.
next prev parent reply other threads:[~2023-04-27 22:05 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 0:04 [PR PATCH] " zlice
2023-03-29 0:05 ` [PR PATCH] [Updated] " zlice
2023-03-29 0:06 ` zlice
2023-03-29 0:12 ` zlice
2023-03-29 0:16 ` zlice
2023-03-29 1:17 ` zlice
2023-04-27 22:05 ` ja-cop [this message]
2023-04-27 23:45 ` zlice
2023-04-27 23:47 ` zlice
2023-04-28 13:31 ` [PR PATCH] [Updated] " zlice
2023-04-28 13:33 ` zlice
2023-04-28 13:33 ` zlice
2023-04-28 13:34 ` zlice
2023-04-28 13:34 ` zlice
2023-05-01 20:03 ` ja-cop
2023-07-31 1:52 ` github-actions
2023-08-02 14:00 ` zlice
2023-10-09 4:57 ` cy1der
2023-11-20 13:04 ` [PR PATCH] [Updated] " zlice
2023-12-03 14:31 ` zlice
2023-12-03 14:32 ` zlice
2024-02-03 20:39 ` [PR PATCH] [Updated] " zlice
2024-02-03 20:39 ` zlice
2024-02-03 20:41 ` zlice
2024-02-03 20:41 ` zlice
2024-02-03 20:42 ` [PR PATCH] [Updated] " zlice
2024-02-15 20:31 ` zlice
2024-02-25 16:20 ` motorto
2024-02-25 17:13 ` [PR PATCH] [Updated] " zlice
2024-02-25 17:15 ` zlice
2024-02-25 17:16 ` [WIP] " zlice
2024-02-25 17:21 ` motorto
2024-02-25 17:23 ` zlice
2024-03-16 11:41 ` basiliscos
2024-04-18 15:30 ` [PR PATCH] [Updated] " zlice
2024-04-18 15:32 ` zlice
2024-04-19 9:57 ` nodatapoints
2024-05-12 0:55 ` [PR PATCH] [Updated] " zlice
2024-05-12 0:56 ` zlice
2024-05-16 21:22 ` [PR PATCH] [Updated] " zlice
2024-05-16 21:24 ` zlice
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=20230427220505.tMnlu6Al5CVpbcMOtHQPTYUS6LeJ5Rn1-xj15jIhq7I@z \
--to=ja-cop@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).