| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
The list of copyright holders could be incomplete. Please update
directly or notify me if your name is missing.
|
| |
|
|
|
| |
Otherwise, when it is called from within a driver, the caller cannot
free the returned data (on Windows).
|
| |
|
|
|
| |
Added for completeness. It makes sense to have such mechanism, but I am
not aware of any user of that..
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Driver loading is now splitted into two stages. In the first stage, an
_EGLModule is created for each driver: user driver, default drivers, and
all files in the search directories that start with "egl_". Modules are
not loaded at this stage.
In the second stage, each module is loaded to initialize a display. The
process stops at the first module that can initialize the display.
If eglGetProcAddress is called before eglInitialize, the same code path
will be taken to find the first module that supports
EGL_DEFAULT_DISPLAY. Because we do not want to initialize the display,
drv->Probe is used instead in this case.
|
|
|
Dynamic arrays will be used to store configs and screens of a display.
|
