On 17.08.2010 17:48, Luca Barbieri wrote: >> Well I don't like drivers changing the hints flag on their own, >> overwriting what the state tracker set. Hence the suggestion to just >> always use normalized coords unless the driver can't handle it (which >> can be a usual global query). > > In my second patchset, those flags are owned by the driver, and the > state tracker must pass them as 0 (instead, the state tracker uses > bind flags, which are distinct, to express its requirement). > This is an improvement over the first one, where indeed the driver > overrode the state tracker in a weird way. > Why don't you like this? Because there is some expectation (with the exception of the private flags) this is state set by the state tracker. Though I guess this isn't too bad.
> >>> llvmpipe would probably prefer unnormalized coords at least in some >>> cases since it saves a multiplication. >> This is possible but I don't think we'd care enough. > I agree, but it's trivial to support this once you support both > normalizations. Roland _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
