On Mon, Nov 18, 2013 at 06:32:31PM -0800, Rodrigo Vivi wrote: > From: Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx> > > When the hardware frame counter reads 0xffffff and we're already past > vblank start, we'd return 0x1000000 as the vblank counter value. Once > we'd cross into the next frame's active portion, the vblank counter > would wrap to 0. So we're reporting two different vblank counter values > for the same frame. > > Fix the problem by masking the cooked value by 0xffffff to make sure > the counter wraps already after vblank start. > > Signed-off-by: Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@xxxxxxxxx> Already applied: edc08d0a40f7ddab6bf7249e59ecf692d36c7192 -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
