search

bennycen / angleproject

Automatically exported from code.google.com/p/angleproject
Other
0 stars 0 forks source link

EGL_ANGLE_device_d3d is needed for applications that want to access the D3D device #935

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
EGL_ANGLE_device_d3d is needed for applications that want to access the D3D 
device directly associated with the configured EGL display.

Original issue reported on code.google.com by co...@microsoft.com on 4 Mar 2015 at 8:28

GoogleCodeExporter commented 9 years ago 
Project: angle/angle
Branch : master
Author : Jamie Madill <jmadill@chromium.org>
Commit : 33d12cb9299324e260bd367b065953314d7c4847

Code-Review  0 : Cooper Partin, Geoff Lang, Shannon Woods
Code-Review  +2: Jamie Madill
Verified     0 : Cooper Partin, Geoff Lang, Shannon Woods
Verified     +1: Jamie Madill
Commit Queue   : Chumped
Change-Id      : I8079661f00d11717ed0e792c9fe8dc5c26f67dcc
Reviewed-at    : https://chromium-review.googlesource.com/252110

Add drafts for device query extensions.

These extensions give power apps the ability to query raw device
pointers from the EGL layer. EGL_EXT_device_query is based on
EGL_EXT_device_base, which is being split into device_query and
device_enumerate. We remove the device enumeration logic, and only
allow the app to query the current device from a display, which
matches how ANGLE works internally.

EGL_ANGLE_device_d3d gives the app the ability to query D3D
devices associated with a display.

BUG=angleproject:935

extensions/EGL_ANGLE_device_d3d.txt
extensions/EGL_EXT_device_query.txt

Original comment by bugdro...@chromium.org on 1 Apr 2015 at 7:19