| author | Rob Clark <rob@ti.com> | |
| Thu, 12 Jan 2012 00:20:18 +0000 (18:20 -0600) | ||
| committer | Rob Clark <rob@ti.com> | |
| Fri, 13 Jan 2012 17:22:43 +0000 (11:22 -0600) | ||
| commit | dc9dfae85f40fa3c981c45f8db68d3ce6d7b0ca6 | |
| tree | f4e9961e02a877dc9b61eff86ab20f127a323d44 | tree | snapshot (tar.xz tar.gz zip) |
| parent | e450d4195cf84c7a9e0bc4a8061d3b53d06f80e7 | commit | diff |
fix issue initialization order vs damage
Damage must be initialized after EXA, otherwise they end up wrapping
the ScreenPtr fxns in wrong order, which ends up resulting in GCOps
fxns getting wrapped in the wrong order. And since Damage gets
indirectly initialized from miDCInitialize() this must happen after
EXA initialization. Otherwise only sw fallback operations will
generate damage.
Damage must be initialized after EXA, otherwise they end up wrapping
the ScreenPtr fxns in wrong order, which ends up resulting in GCOps
fxns getting wrapped in the wrong order. And since Damage gets
indirectly initialized from miDCInitialize() this must happen after
EXA initialization. Otherwise only sw fallback operations will
generate damage.
| src/omap_driver.c | diff | blob | history |