| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
https://bugs.freedesktop.org/show_bug.cgi?id=29162
|
|
|
|
|
|
|
| |
Only refresh the fake front buffer if there is one, and only destroy the region
once.
Fixes X11 protocol errors reported by 'mcgreg' on IRC.
|
|
|
|
| |
We do this in the X server for DRI2.
|
| |
|
|
|
|
|
| |
The XIDs are display wide so the natural location of the hash is here.
This way we don't have to lookup in each of the screen hashes.
|
| |
|
|
|
|
|
| |
The DRI2 protocol for ust, msc and sbc are unsigned but the extensions
talk about int64_t. Do a little dance to make the compiler shut up.
|
| |
|
|
|
|
|
| |
The extension never worked, the implementation returns GLX_BAD_CONTEXT
when enabling the frame tracking.
|
| |
|
| |
|
| |
|
|
|
|
| |
Only r200 implemented it.
|
|
|
|
|
|
| |
GLXscreenConfigs is badly named and a dumping ground for a lot of stuff.
This patch creates private screen structs for the dri drivers and moves
some of their fields over there.
|
|
|
|
| |
Enough is enough.
|
| |
|
|
|
|
| |
This saves a superfluous flush and a create/destryo region.
|
|
|
|
|
|
| |
DRI2 events are sent to the X drawable ID used to create the DRI2 drawable,
not the GLX drawable ID. So when an event comes in, we need to look up
the __GLXDRIdrawable by its X drawable ID, which needs a new hash table.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When direct rendering is being used, DRI2 BufferSwapComplete events are
sent unconditionally to clients, even if they haven't been requested.
This causes error messages to be printed by every freeglut application
of the form
freeglut (./gears): Unknown X event type: 104
and might confuse other clients.
This is a fixed up version of the patch by Jesse Barnes, which drops
BufferSwapComplete events if they are not requested by clients.
Fixes fdo bug 27962.
Signed-off-by: Nick Bowler <[email protected]>
Signed-off-by: Jesse Barnes <[email protected]>
|
|
|
|
|
| |
Signed-off-by: Fernando Carrijo <[email protected]>
Signed-off-by: Brian Paul <[email protected]>
|
| |
|
| |
|
|
|
|
|
| |
When we don't get invalidate events, we need to invalidate a drawable
before using it for tfp to make sure we have uptodate buffers.
|
|
|
|
|
| |
This introduces a new per-context vtable, which lets us clean up all the
#ifdef's a bit and move the DRI2 specific implementation into dri2_glx.c.
|
|
|
|
|
|
|
|
|
|
| |
The backwards compatibility code calls the DRI driver invalidate hook
on swap buffer and flush front buffer. This lets the DRI driver rely
on invalidate callbacks and drop the glViewport() hack, even if the
server doesn't send invalidate events. This is essentially a revert
of 2d00d16da7f5d2255cb37b48edaf4cbb9ca7e930, except that we now also
pass the __DRI_USE_INVALIDATE extension even when the server doesn't
have DRI2 invalidate events.
|
| |
|
|
|
|
|
|
|
| |
When we have DRI2 protocol at least 2.3, we get an event from the
server when the back buffers get invalidated. When that's the case
let the driver know that it can rely on invalidate instead of the
glViewport polling.
|
|
|
|
|
|
|
|
|
| |
We only need this when the server may have swapped the buffers or
when we receive an invalidate event from the server. The default
behaviour is still that the DRI driver will invalidate its own buffers
when glViewport is called.
https://bugs.freedesktop.org/show_bug.cgi?id=27277
|
|
|
|
|
|
|
|
| |
And lookup the GLX screen for the context. Otherwise we'll end up
jumping through a NULL-pointer once we try to look up the visual
or config for the shared context.
https://bugs.freedesktop.org/show_bug.cgi?id=14245
|
|
|
|
|
| |
This was missed in commit 296adbd545b8efd38c9ed508166b2de2764a444b.
Fixes darwin build.
|
|
|
|
| |
Move glapi to src/mapi/{glapi,es1api,es2api}.
|
|
|
|
|
|
|
|
|
| |
This is a regression from e42d84eaba228d4d96a46d116c6ca24581e29439
https://bugs.freedesktop.org/show_bug.cgi?id=27929
Signed-off-by: Jeremy Huddleston <[email protected]>
(cherry picked from commit 4d63be67f320839d115987211d0d9b4297f6d17d)
|
|
|
|
| |
update for fbconfig_style_tags
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
src/glx/dri2_glx.c
src/glx/glx_pbuffer.c
|
| |
| |
| |
| | |
Signed-off-by: Brian Paul <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Jeremy Huddleston <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Jeremy Huddleston <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Jeremy Huddleston <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Jeremy Huddleston <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Jeremy Huddleston <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Jeremy Huddleston <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Jeremy Huddleston <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Jeremy Huddleston <[email protected]>
|
| |
| |
| |
| |
| |
| | |
There is a user somewhere that tests it before its initial set.
Signed-off-by: Eric Anholt <[email protected]>
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
tags.
__glXInitializeVisualConfigFromTags doesn't skip the payload of
unrecognized tags. Instead, it treats the value as if it were the
next tag, which can happen if the server's GLX extension is not
Mesa's. For example, this falls down when NVIDIA sends a
GLX_FLOAT_COMPONENTS_NV = 0 pair, causing
__glXInitializeVisualConfigFromTags to bail out early.
Signed-off-by: Aaron Plattner <[email protected]>
Signed-off-by: Ian Romanick <[email protected]>
|
|\| |
|
| | |
|