| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
The assertion is wrong, now that state tracker can cope with a window with
zero width or height.
|
| |
|
|
|
|
| |
Localizes preprocessor usage to one place.
|
| |
|
|
|
|
|
| |
We need to distinguish surfaces for mouse cursors from scanouts,
because nv50 hardware display engine ignores tiling flags.
|
|
|
|
|
|
|
|
|
|
| |
We use a hidden window for pbuffer contexts, but Windows limits window
sizes to the desktop size by default. This means that creating a big
pbuffer on a small resolution single monitor would truncate the pbuffer
size to the desktop.
This change overrides the windows maximum size, allow to create windows
arbitrarily large.
|
|
|
|
| |
While ensuring the framebuffer area is never zero.
|
|
|
|
|
| |
We need cursor data to land in destination buffer before drmModeSetCursor.
It fixes "cursor lag" on nv50.
|
| |
|
| |
|
|
|
|
| |
Lockup happens when wl_drm interface is not available.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
When the window is minimized GetClientRect will return zeros.
Instead of creating a 1x1 framebuffer, simply preserve the current window
size, until the window is restored or maximized again.
|
| |
|
|
|
|
|
|
|
|
|
| |
Because:
- bindings are not fully automatic, and they are broken most of the time
- unit tests/samples can be written in C on top of graw
- tracing/retracing is more useful at API levels with stable ABIs such as
GL, producing traces that cover more layers of the driver stack and and
can be used for regression testing
|
|
|
|
| |
Thanks to Brian Paul for diagnosing the issue.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The drivers have been changed so that they behave as if all of the flags
were set. This is already implicit in most hardware drivers and required
for multiple contexts.
Some state trackers were also abusing the PIPE_FLUSH_RENDER_CACHE flag
to decide whether flush_frontbuffer should be called.
New flag ST_FLUSH_FRONT has been added to st_api.h as a replacement.
|
| |
|
|
|
|
| |
So that they don't have the driver-specific param and return type.
|
|
|
|
| |
Only st/xorg used it and even incorrectly with regards to pipelined transfers.
|
|
|
|
|
|
|
| |
Without this, EXT_texture_from_pixmap is trivially broken. With it,
it's merely subtly broken.
Signed-off-by: Adam Jackson <[email protected]>
|
| |
|
|
|
|
| |
I don't see a reason we need them.
|
| |
|
|
|
|
|
|
| |
This is a follow-up to commit b39bccbd4ed71e9585da4cf5acf7b887b2e90899.
Fixes Linux SCons build.
|
|
|
|
|
| |
This is a follow-up to the ARB_sync patch for st/mesa and completes
the ARB_sync implementation.
|
| |
|
| |
|
|
|
|
|
| |
This hopefully fixes wayland-egl's dependency
resolution for autogenerated wayland-drm headers.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When doing copy swapbuffers using drm, throttle on outstanding copy operations.
Introduces a new environment variable, EGL_THROTTLE_FENCES that the
user can use to indicate the desired number of outstanding swapbuffers, or
disable throttling using EGL_THROTTLE_FENCES=0.
This can and perhaps should be extended to the pageflip case as well, since
with some hardware pageflips can be pipelined. In case the pageflip syncs, the
throttle operation will be a no-op anyway.
Update copyright notices.
Signed-off-by: Thomas Hellstrom <[email protected]>
|
|
|
|
|
|
|
|
| |
Use the pageflip ioctl when available.
Otherwise, or when the backbuffer contents need to be preserved,
fall back to a copy operation.
Signed-off-by: Thomas Hellstrom <[email protected]>
|
|
|
|
|
|
|
| |
The copy swap can be used when we need to preserve the contents of
the back buffer or when there is no way to do native page-flipping.
Signed-off-by: Thomas Hellstrom <[email protected]>
|
|
|
|
|
|
|
|
| |
This makes it usable also for native helpers.
Also add inline functions to access the context and to
uninit the native display structure.
Signed-off-by: Thomas Hellstrom <[email protected]>
|
|
|
|
|
|
| |
whats one more between friends.
again bnf on irc.
|
|
|
|
|
|
| |
Init array size to 1,
reported by bnf on irc.
|
|
|
|
| |
reported by bnf on irc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Needs to track this ourself since because we get into a race condition with
the dri_util.c code on make current when rendering to the front buffer.
This is what happens:
Old context is rendering to the front buffer.
App calls MakeCurrent with a new context. dri_util.c sets
drawable->driContextPriv to the new context and then calls the driver make
current. st/dri make current flushes the old context, which calls back into
st/dri via the flush frontbuffer hook. st/dri calls dri loader flush
frontbuffer, which calls invalidate buffer on the drawable into st/dri.
This is where things gets wrong. st/dri grabs the context from the dri
drawable (which now points to the new context) and calls invalidate
framebuffer to the new context which has not yet set the new drawable as its
framebuffers since we have not called make current yet, it asserts.
|
|
|
|
|
|
| |
This is a follow-up to commit eafb7f234d11a290b00dcaf5492b9bdad1cf5148.
Fixes Linux SCons build.
|
|
|
|
|
| |
And set a reasonable buffer usage flag everywhere instead of
just PIPE_USAGE_DEFAULT.
|