On Wed, Aug 11, 2010 at 5:41 PM, Luca Barbieri <l...@luca-barbieri.com>wrote:
> > I'm completely okay with this iteration of this patchset, since it > > requires no Gallium API changes and seems very straightforward. I do > > have a question, though, since I'm so unfamiliar with nvfx. In r300g > > there is a fragment program rewrite to normalize texcoords > > unconditionally for r300 and conditionally for r500. This is also how > > we fake our NPOT support. Is this kind of rewriting truly impossible > > for nvfx, or just time-consuming? > > It's possible (but time-consuming and likely with significant overhead). > But even then it would be somewhat silly to make things like blitter > go through it. > I am not sure if the following is legal, but I think we will just mask this unnormalized flag out in resource_create, because r300 doesn't like (read: doesn't support in hardware) unnormalized texture coordinates, and switching shaders just because of the flag is silly. -Marek
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
