On Fri, 08 Jul 2011 20:43:47 +0100, Chris Wilson <[email protected]> wrote:
> Bumping to 250ms sufficiently delays the task to miss the race, but we > can not foretell just how long any given crtc modeset will take. So what > we need is to take the mode_config.lock in order to prevent concurrent > access to the FBC registers and also to prevent the fb from disappearing > beneath us: Sounds like we also need to push out any FBC reconfiguration anytime modesetting occurs to ensure that we've waited past a vblank interval? -- [email protected]
pgpcHxI798TPE.pgp
Description: PGP signature
_______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
