<div class="gmail_quote">On Wed, Aug 11, 2010 at 5:41 PM, Luca Barbieri <span dir="ltr"><<a href="mailto:luca@luca-barbieri.com">luca@luca-barbieri.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">> I'm completely okay with this iteration of this patchset, since it<br>
> requires no Gallium API changes and seems very straightforward. I do<br>
> have a question, though, since I'm so unfamiliar with nvfx. In r300g<br>
> there is a fragment program rewrite to normalize texcoords<br>
> unconditionally for r300 and conditionally for r500. This is also how<br>
> we fake our NPOT support. Is this kind of rewriting truly impossible<br>
> for nvfx, or just time-consuming?<br>
<br>
</div>It's possible (but time-consuming and likely with significant overhead).<br>
But even then it would be somewhat silly to make things like blitter<br>
go through it.<br></blockquote></div><br>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.<br><br>-Marek<br>