Mesa (nvfx-next-3): u_blitter: add missing sampler_state-> normalized_coords = 1 (how can this be?!?)

[Luca Barbieri]

Module: Mesa
Branch: nvfx-next-3
Commit: 5d74dfbbf8a62b42017ac9657ae82a4929a685bc
URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=5d74dfbbf8a62b42017ac9657ae82a4929a685bc

Author: Luca Barbieri <luca at luca-barbieri.com>
Date:   Wed Apr 14 06:14:13 2010 +0200

u_blitter: add missing sampler_state->normalized_coords = 1 (how can this be?!?)

It's using normalized texcoords, but not setting it in the sampler state.

How can this possibly work with r300g though?
Am I missing something?

Perhaps r300g compensates with another bug that causes it to ignore the
request to use unnormalized texcoords?

---

 src/gallium/auxiliary/util/u_blitter.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/src/gallium/auxiliary/util/u_blitter.c b/src/gallium/auxiliary/util/u_blitter.c
index 104cbf7..ba599e1 100644
--- a/src/gallium/auxiliary/util/u_blitter.c
+++ b/src/gallium/auxiliary/util/u_blitter.c
@@ -168,6 +168,7 @@ struct blitter_context *util_blitter_create(struct pipe_context *pipe)
    sampler_state->wrap_s = PIPE_TEX_WRAP_CLAMP_TO_EDGE;
    sampler_state->wrap_t = PIPE_TEX_WRAP_CLAMP_TO_EDGE;
    sampler_state->wrap_r = PIPE_TEX_WRAP_CLAMP_TO_EDGE;
+   sampler_state->normalized_coords = 1;
    /* The sampler state objects which sample from a specified mipmap level
     * are created on-demand. */