This is less of an issue for me now, since upstream has started fixing my bugs instead of just claiming my hardware is broken or assigning them all to Keith Packard :-). I'm now using the new intel driver (locally compiled from a git snapshot with some recent fixes) and it's working acceptably for me, so AFAIC this bug can be closed. Thanks!