[PATCH v2 1/2] radeon: Don't generate new fence for page flip.

2011/7/13 Michel D?nzer : > From: Michel D?nzer > > Use the fence of the new frontbuffer, if any. > > Generating a new fence could cause us to wait for completely unrelated > rendering to finish before performing the flip. > > Signed-off-by: Michel D?nzer Reviewed-by: Alex Deucher > --- > > v2

Re: [PATCH v2 1/2] radeon: Don't generate new fence for page flip.

2011/7/13 Michel Dänzer : > From: Michel Dänzer > > Use the fence of the new frontbuffer, if any. > > Generating a new fence could cause us to wait for completely unrelated > rendering to finish before performing the flip. > > Signed-off-by: Michel Dänzer Reviewed-by: Alex Deucher > --- > > v2

[PATCH v2 1/2] radeon: Don't generate new fence for page flip.

From: Michel D?nzer Use the fence of the new frontbuffer, if any. Generating a new fence could cause us to wait for completely unrelated rendering to finish before performing the flip. Signed-off-by: Michel D?nzer --- v2: * Rebase against drm-core-next. * Leave radeon_fence_unref() call in e

[PATCH v2 1/2] radeon: Don't generate new fence for page flip.

From: Michel Dänzer Use the fence of the new frontbuffer, if any. Generating a new fence could cause us to wait for completely unrelated rendering to finish before performing the flip. Signed-off-by: Michel Dänzer --- v2: * Rebase against drm-core-next. * Leave radeon_fence_unref() call in e