non-affine transforms require floating point computation
@keithp
Submitted by Keith Packard Assigned to Søren Sandmann Pedersen
Description
Under a non-affine transform, or, in fact, any transform where the 'w' component of the (u,v,w) homogeneous source coordinate is not 1, the representation of u,v,w as 16.16 fixed point numbers will over/under flow on a regular basis even given fairly mundane transformations (like a simple keystone correction). I've fixed the intel driver to do these computations in floating point; I'm not sure we want to try to use fixed point here.
Version: git master