[EMAIL PROTECTED] wrote:
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=5365
Summary: ut2k4 locks if future_hw_tcl_on=hw_tcl_on=1
Product: Mesa
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Drivers/DRI/r300
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED],[EMAIL PROTECTED]
Dates back to when t_vp_build.c was made depend on fragment programs.
I have tracked this down and it seems that the lock is caused by having tmu
enabled but frag prog not reading inputs to it.
Aapo,
Can you give me a little more context? Is there some aspect in the r300
hardware that is requiring these values even though the fragment program doesn't
use them?
Is it possible that the fragment program being referenced by t_vp_build.c is
somehow out of sync with the one uploaded onto hardware?
Is the fragment program one supplied by the user, or is it generated by
texenvprogram.c?
What is the problem with col0?
Keith
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
