| Age | Commit message (Collapse) | Author |
|---|
|
A platform is already used to mean a window system in EGL. No need to
use a different term.
|
|
The backend is pure software. It implements EGL_MESA_screen_surface
extension, and is kept simple by only exporting the current mode.
|
|
|
|
If no customizer is present, 3D will be enabled by default.
Otherwise the option will default to the customizer value.
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
|
|
Forgot to stage this chunk in last commit.
|
|
The code is shared by ximage and gdi backend.
|
|
Conflicts:
src/gallium/state_trackers/python/p_context.i
|
|
more consistent with rest of gallium naming conventions.
Also rename driver-internal names for these the same.
|
|
This lets us specify linear interpolation instead of perspective
interpolation for blit operations. Might be a bit faster.
|
|
The xorg state tracker gets two new options to let the user choose
whether to enable / disable dirty throttling and swapbuffer throttling.
The default value of these options are enabled, unless the winsys
supplies a customizer with other values. The customizer record has been
extended to allow this, and also to set winsys-based throttling on a per-
context basis.
The vmware part of this patch disables the dirty throttling if the kernel
supports command submission throttling, and also in that case sets kernel
based throttling for everything but swapbuffers. The vmware winsys does not
set throttling per context, even if it theoretically could, but instead
sets throttling per screen. This should perhaps be changed, should the
xorg state tracker start to use multiple rendering contexts. Kernel throttling
is off by default for all new screens/contexts, so the dri state tracker
is not affected.
This significantly improves interactivity of the vmware xorg driver.
Cherry-picked from commit a8f3b3f88acc1f0193fa740e76e9d815f07f32ab
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
Signed-off-by: Jakob Bornecrantz <jakob@vmware.com>
|
|
Due to a quantization error, different cliprects of scaled video windows may
not have identical x / y scale.
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
|
|
We don't support it yet since we don't implement the shadow allocate
functions.
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
|
|
resource_surface_add_resources should still be called even when the
stamps match. For example, a caller may ask for two different sets of
attachments.
|
|
This fixes an uninitialised value use in the dri2 st when doing TFP.
It uses the driContextPriv which isn't initialised at alloc time.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
|
|
|
|
|
|
There is only resource_surface for now. It helps manage the resources
of a software-based native surface such as XImage or GDI.
|
|
Fix several portability issues and add SConscript for Windows build.
|
|
At least, .dll is used on Windows.
|
|
The backend uses Windows GDI driver to provide a software EGL
implementation on Windows.
|
|
surface_copy/fill
|
|
Match MALLOC with FREE. Otherwise, it causes weird segfaults when built
with memory debugging.
|
|
This is some refactoring works. Creating a pbuffer from an
EGL_OPENVG_IMAGE is still not supported.
|
|
It was broken since surface_copy -> resource_copy_region transition.
|
|
Check if the native native is EGL_DEFAULT_DISPLAY. If not, treat it as
an fd.
|
|
|
|
|
|
|
|
|
|
This was missed in commit f501230db3a94c9328b8e769d9c17b2c3792e19c.
Fixes SCons build.
|
|
With the removal of DRI1 support there where no use of this argument,
some drivers didn't even properly check it.
|
|
Nobody used it and the current code had been trough so many
changes yet never once being tested.
|
|
|
|
|
|
|
|
|
|
|
|
Conflicts:
src/mesa/state_tracker/st_gen_mipmap.c
src/mesa/state_tracker/st_texture.c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
compile tested only.
Should probably change the python surface_copy/fill functions
also into resource_copy/fill_region functions and adapt the code
using them.
|
|
The linux-debug target builds...
|
|
|
