| Summary: | Using glXBindTexImageEXT with a GLXPixmap created out-of-process fails | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Andrew Comminos <andrew> |
| Component: | GLX | Assignee: | mesa-dev |
| Status: | RESOLVED MOVED | QA Contact: | mesa-dev |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
(In reply to Andrew Comminos from comment #0) > I suggest that driFetchDrawable is used in dri{2,3}_bind_tex_image, as it is > in dri{2,3}_bind_context. Have you tried that? If it works, I'd send such a patch to mesa-dev@lists.freedesktop.org for review/inclusion. -- 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/104. |
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.
When binding a GLXPixmap created in a different process using glXBindTexImageEXT, we only bind a black texture. I believe this occurs because the associated DRI drawable is stored in the underlying display- when dri{2,3}_bind_tex_image is called with a different glx_display than the one that created (or bound) the GLXPixmap, we find that its drawable table does not contain the associated DRI drawable, and we return. I suggest that driFetchDrawable is used in dri{2,3}_bind_tex_image, as it is in dri{2,3}_bind_context.