From 31c1ea5ed4e90b76adcb51bf1224dce643a4f701 Mon Sep 17 00:00:00 2001 From: Kenneth Graunke Date: Fri, 26 Oct 2012 11:01:57 -0700 Subject: i965: Update comment about clipper constants. The old VS backend doesn't exist, but I believe these still need to be delivered to the clipper thread. Reviewed-by: Eric Anholt --- src/mesa/drivers/dri/i965/brw_curbe.c | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) (limited to 'src/mesa/drivers/dri/i965/brw_curbe.c') diff --git a/src/mesa/drivers/dri/i965/brw_curbe.c b/src/mesa/drivers/dri/i965/brw_curbe.c index 8f196f4..b55453a 100644 --- a/src/mesa/drivers/dri/i965/brw_curbe.c +++ b/src/mesa/drivers/dri/i965/brw_curbe.c @@ -207,15 +207,7 @@ brw_upload_constant_buffer(struct brw_context *brw) } } - - /* When using the old VS backend, the clipplanes are actually delivered to - * both CLIP and VS units. VS uses them to calculate the outcode bitmasks. - * - * When using the new VS backend, it is responsible for setting up its own - * clipplane constants if it needs them. This results in a slight waste of - * of curbe space, but the advantage is that the new VS backend can use its - * general-purpose uniform layout code to store the clipplanes. - */ + /* clipper constants */ if (brw->curbe.clip_size) { GLuint offset = brw->curbe.clip_start * 16; GLuint j; -- cgit v1.1