From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 79431] New: OpenGL OpenCL interop results in corrupted renderbuffer object image
Date: Thu, 29 May 2014 23:35:00 +0000 [thread overview]
Message-ID: <bug-79431-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1121 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=79431
Priority: medium
Bug ID: 79431
Assignee: dri-devel@lists.freedesktop.org
Summary: OpenGL OpenCL interop results in corrupted
renderbuffer object image
Severity: normal
Classification: Unclassified
OS: All
Reporter: pavol@klacansky.com
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
I use APP SDK with OpenCL running on CPU and r600 driver on GPU (AMD Mobility
3650) to compute image. If I use OpenCL image, I get correct result, however if
I want to display image using OpenGL (interop), it is corrupted.
I create renderbuffer object, than link it with OpenCL
(clCreateFromGLRenderbuffer) and then after image was computed I blit it
to back buffer.
I tested it in lab on nVidia proprietary driver and it works well, I suspect
the problem is in renderbuffer sharing.
OpenCL is 1.2, OpenGL 3.3.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2425 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 reply other threads:[~2014-05-29 23:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 23:35 bugzilla-daemon [this message]
2014-05-30 10:04 ` [Bug 79431] OpenGL OpenCL interop results in corrupted renderbuffer object image bugzilla-daemon
2014-06-05 10:26 ` bugzilla-daemon
2014-06-09 19:14 ` bugzilla-daemon
2017-03-22 15:20 ` bugzilla-daemon
2017-03-23 20:24 ` bugzilla-daemon
2019-09-18 19:16 ` 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-79431-502@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).