Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • mesa mesa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2,710
    • Issues 2,710
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 908
    • Merge requests 908
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mesa
  • mesamesa
  • Issues
  • #2119
Closed
Open
Created Nov 18, 2019 by Robert Mader@rmader

Expose OES_EGL_image_external and OES_EGL_image_external_essl3 extensions in GL core profile

Currently the GL core profile exposes the GL_OES_EGL_image, but not GL_OES_EGL_image_external and GL_OES_EGL_image_external_essl3. In some situations, especially when dealing with DMABUFs, they can be quite handy and there seems to be no equivalent in desktop GL. Update: see #2119 (comment 315982)

Potentially all three should then get exported as GL_ARB instead of GL_OES.


Experimental untested patch: https://gist.githubusercontent.com/karolherbst/111946258289d29595bb037dda724685/raw/8e35a050154ffcaf0dccfedd454a79abe3c35d8d/image_external.patch

Edited Nov 19, 2019 by Robert Mader
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking