Summary: | [OpenCL] Please add Image support | ||
---|---|---|---|
Product: | Mesa | Reporter: | Thomas Paris <mercen45> |
Component: | Gallium/StateTracker/Clover | Assignee: | mesa-dev |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | enhancement | ||
Priority: | medium | CC: | ao2, darkbasic, julien.isorce, matti.niemenmaa+freedesktopbugs, mercen45, pbrobinson, serge, shi1986000, tjaalton |
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 74974, 82717, 99553, 107115, 109224 |
Description
Thomas Paris
2014-12-26 09:45:32 UTC
Hi, I still get this when running darktable with mesa 17: [opencl_init] discarding device 0 `AMD REDWOOD (DRM 2.48.0 / 4.9.0-2-amd64, LLVM 4.0.0)' due to missing image support. Is it the driver that lack support for that functionality or is it rather a limitation of the device itself? My device is an "ATI Radeon HD 5670". Thanks, Antonio In case anyone works on it, I have saved Zoltan Gillian's patches here: https://github.com/vedranmiletic/mesa/tree/r600-image-support funfunctor has also worked on it a bit: https://cgit.freedesktop.org/~funfunctor/mesa/log/?h=clover-image-support https://cgit.freedesktop.org/~funfunctor/mesa/log/?h=clover-image-support-enabled I see there are clover patches for image support already upstream e.g. f2c52e392 clover: Implement CL1.2 clCreateImage(). 2518645f6 clover: Implement clCreateImage?D w/ clCreateImage. What is missing? Driver-specific patches for radeonsi / r600? Any pointers/guidance would be welcome. Is there any progress at all towards this? I feel like it would really improve Linux use case for some of us using software like Darktable and whatever other software could possibly use this, I'm still unable to use opencl in Darktable with the same error: 0.021473 [opencl_init] found opencl runtime library 'libOpenCL' 0.021502 [opencl_init] opencl library 'libOpenCL' found on your system and loaded 0.081308 [opencl_init] found 1 platform 0.081325 [opencl_init] found 1 device 0.081354 [opencl_init] discarding device 0 `AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 3.27.0, 5.0.0-8-generic, LLVM 8.0.0)' due to missing image support. 0.081359 [opencl_init] no suitable devices found. 0.081360 [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system. (In reply to smt from comment #5) > Is there any progress at all towards this? I feel like it would really > improve Linux use case for some of us using software like Darktable and > whatever other software could possibly use this, I'm still unable to use > opencl in Darktable with the same error: > > 0.021473 [opencl_init] found opencl runtime library 'libOpenCL' > 0.021502 [opencl_init] opencl library 'libOpenCL' found on your system and > loaded > 0.081308 [opencl_init] found 1 platform > 0.081325 [opencl_init] found 1 device > 0.081354 [opencl_init] discarding device 0 `AMD Radeon (TM) RX 460 Graphics > (POLARIS11, DRM 3.27.0, 5.0.0-8-generic, LLVM 8.0.0)' due to missing image > support. > 0.081359 [opencl_init] no suitable devices found. > 0.081360 [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system. There has been little progress on image support. The implementation had tons of other problems with advertised functionality (mostly in libclc builtins). You'd probably get incorrect results if those workloads ran. images are #3 on my todo list (after fixing conversion routines(#1) and support for non-inlined function calls(#2)) unless someone beats me to it. but time is scarce. It would be really nice to have it in place. There are a lot of of pre-GCN 1.1 card out there capable to work with opencl. In fact, I was practically forced to upgrade my nice GCN 1.0 card solely because of darktable's needs when I gave up waiting AMD to fix their binary opencl driver... *** Bug 111403 has been marked as a duplicate of this bug. *** *** Bug 111404 has been marked as a duplicate of this bug. *** -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/130. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.