Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | glx: Suppress BadDrawable from DRI2CopyRegion | Kristian Høgsberg | 2010-03-22 | 1 | -1/+14 |
| | | | | | | | | | | This can happen when an X window is destroyed behind our back. We use DRI2CopyRegion behind the scenes in many places (like flushing the fake front to the real front) so we have to ignore X errors triggered in that case. The glean test cases trigger this consistently as they don't destroy the GLX drawable nicely, they just destroy the X window. | ||||
* | glx: Fix a couple of warnings | Kristian Høgsberg | 2010-02-16 | 1 | -2/+0 |
| | |||||
* | glx: Only register wire handlers for the events the server supports | Kristian Høgsberg | 2010-02-16 | 1 | -1/+20 |
| | |||||
* | dri2: Event driven buffer validation. | Francisco Jerez | 2010-02-16 | 1 | -1/+9 |
| | | | | | | | | | | | | | | | | | | When a buffer invalidation event is received from the X server, the "invalidate" hook of the DRI2 flush extension is executed: A generic implementation (dri2InvalidateDrawable) is provided that just bumps the "pStamp" sequence number in __DRIdrawableRec. For old servers not supporting buffer invalidation events, the invalidate hook will be called before flushing the fake front/back buffer (that's typically once per frame -- not a lot worse than the situation we were in before). No effort has been made on preserving backwards compatibility with version 2 of the flush extension, but I think it's acceptable because AFAIK no released stack is making use of it. Signed-off-by: Kristian Høgsberg <[email protected]> | ||||
* | Retire miniglx and move the actual glx code up to src/glx | Kristian Høgsberg | 2010-02-09 | 1 | -0/+645 |