https://bugs.freedesktop.org/show_bug.cgi?id=35579
--- Comment #32 from Michel Dänzer <[email protected]> 2011-03-30 00:35:59 PDT --- (In reply to comment #31) > Looks like exa calls CheckComposite in advance to prevent switching back and > forth between hardware & software rendering. Not really, the CheckComposite hook allows the driver to quickly reject operations it won't be able to accelerate, without incurring any overhead required before the PrepareComposite hook, e.g. for migrating pixmap contents into GPU accessible memory. > I was hoping you could tell me the most likely places to check and/or maybe > even a suggestion for how you would go about fixing it. See comment #24 and comment #27 for some examples, but if there were clear, simple steps, somebody probably would have taken them... It would probably be better to take this to the xorg-devel mailing list. > As for exa - would I need to recompile the whole X to make a change to it or > can I play with it as a module? make -C exa && make -C hw/xfree86/exa gives you hw/xfree86/exa/.libs/libexa.so with any changes you made. Obviously, if the changes affect the ABI between EXA and the driver (which should be avoided if feasible for a final solution, but might be useful for prototyping) or the rest of the X server, those will need rebuilding as well. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ xorg-driver-ati mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-driver-ati
