diff options
| author | Sven Gothel <[email protected]> | 2012-09-30 19:47:46 +0200 |
|---|---|---|
| committer | Sven Gothel <[email protected]> | 2012-09-30 19:47:46 +0200 |
| commit | 92398025abdabb2fdef0d78edd41e730991a6f94 (patch) | |
| tree | 8d209c588d1246aa126c29465206ba1f8167c0e2 /make/scripts/targetcommand-loop.sh | |
| parent | 43891be36e8485353ac74f329fd2f7438303a846 (diff) | |
Workaround for Bug 623: Sporadic XCB assertion failures w/ ATI proprietary driver and w/o native X11 locking
The proprietary ATI X11 driver does not handle multi-threaded [GL] clients well,
i.e. triggers an XCB assertion 'from time to time'.
It almost seems like that the driver either:
- aliases all display connections to it's connection name, i.e. server; or
- utilizes a build-in display connection w/o locking, used for some reason
+++
- X11Lib: Add QueryExtension(dpy, name) allowing early driver determination w/o GL
- X11Util detects 'requiresGlobalToolkitLock' and 'markAllDisplaysUnclosable' via
X11 extensions. In case certain ATI extensions are available, both are set to true.
- X11GLXDrawableFactory: Dropped setting 'markAllDisplaysUnclosable', using X11Util's detection (see above).
- New GlobalToolkitLock to satisfy certain driver restrictions (ATI's XCB multithreading bug)
- NativeWindowFactory handles new property requiresGlobalToolkitLock,
in which case the new GlobalToolkitLock is being used instead of ResourceToolkitLock.
- JAWTUtil ToolkitLock locks GlobalToolkitLock 1st to match new 'requiresGlobalToolkitLock' property.
- Document static method requirement of X11Util, GDIUtil and OSXUtil via marker interface ToolkitProperties
- ToolkitLock: New method 'validateLocked()', allowing use to validate whether the device/toolkit
is properly locked and hence to detect implementation bugs. See unit test class: ValidateLockListener
Diffstat (limited to 'make/scripts/targetcommand-loop.sh')
0 files changed, 0 insertions, 0 deletions