summaryrefslogtreecommitdiff
path: root/src/gallium/drivers/i965
diff options
context:
space:
mode:
authorKeith Whitwell <keithw@vmware.com>2009-11-18 14:40:43 -0800
committerKeith Whitwell <keithw@vmware.com>2009-11-18 14:40:43 -0800
commit6b1ede0110f855218119a7a3b26fe3b26aee1bbd (patch)
treef2a829289daa1c9e9c949ccd130f2d8466d3cc4a /src/gallium/drivers/i965
parent1877e6cd2d76143ef8a9c516122afe614ae3b4a4 (diff)
i965g: remove more references to nr_vp_outputs in wm compilation
We're really more concerned about how many inputs the fragment shader is expecting.
Diffstat (limited to 'src/gallium/drivers/i965')
-rw-r--r--src/gallium/drivers/i965/brw_wm_pass2.c4
1 files changed, 1 insertions, 3 deletions
diff --git a/src/gallium/drivers/i965/brw_wm_pass2.c b/src/gallium/drivers/i965/brw_wm_pass2.c
index 56f39d036b..19248b4519 100644
--- a/src/gallium/drivers/i965/brw_wm_pass2.c
+++ b/src/gallium/drivers/i965/brw_wm_pass2.c
@@ -87,11 +87,9 @@ static void init_registers( struct brw_wm_compile *c )
/* XXX: currently just hope the VS outputs line up with FS inputs:
*/
- for (j = 0; j < c->key.vp_nr_outputs; j++)
+ for (j = 0; j < c->key.nr_inputs; j++)
prealloc_reg(c, &c->payload.input_interp[j], reg++);
- assert(c->key.vp_nr_outputs >= 1);
-
c->prog_data.first_curbe_grf = c->key.nr_depth_regs * 2;
c->prog_data.urb_read_length = (c->key.nr_inputs + 1) * 2;
c->prog_data.curb_read_length = c->nr_creg * 2;