Bug 9134 - EdgeFlag within a display list with mode set to COMPILE_AND_EXECUTE doen't take effect.
Summary: EdgeFlag within a display list with mode set to COMPILE_AND_EXECUTE doen't ta...
Status: CLOSED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Eric Anholt
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-22 22:28 UTC by haihao
Modified: 2009-08-24 12:25 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
Test case demonstrating edge flag in a display list with mode set to COMPILE_AND_EXECUTE (2.02 KB, text/plain)
2006-11-22 22:36 UTC, haihao 		Details
Special treatment for EDGEFLAG when loopbacking vertex list (423 bytes, patch)
2006-11-22 22:49 UTC, haihao 		Details | Splinter Review
View All

Description haihao 2006-11-22 22:28:03 UTC 
Calling EdgeFlag from a display list with mode set to COMPILE is OK, but from a
display list with mode set to COMPILE_AND_EXECUTE has no effect, even nothing is
drawn on the window.
Comment 1 haihao 2006-11-22 22:36:51 UTC 
Created attachment 7876 [details]
Test case demonstrating edge flag in a display list with mode set to COMPILE_AND_EXECUTE
Comment 2 haihao 2006-11-22 22:49:43 UTC 
Created attachment 7877 [details] [review]
Special treatment for  EDGEFLAG when loopbacking vertex list

Because BRW_ATTRIB_EDGEFLAG, BRW_ATTRIB_INDEX are between 0 and
BRW_ATTRIB_TEX7, they will be included when brw_loopback_vertex_list(in
brw_fallback.c) sets vertex attribute function in the first loop.

I modified it to exclude BRW_ATTRIB_EDGEFLAG and BRW_ATTRIB_INDEX in the first
loop.
Comment 3 haihao 2006-11-23 17:49:19 UTC 
The CVS HEAD revision now works fine, Thanks for Keith's committing.
Comment 4 haihao 2006-11-23 17:50:14 UTC 
Verified
Comment 5 Adam Jackson 2009-08-24 12:25:10 UTC 
Mass version move, cvs -> git

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.