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
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2005-12-19 09:45 -------
(In reply to comment #2)
> I don't really agree with this patch, on two levels:
>
> 1) I believe the programs generated by t_vp_build.c are doing the right
> thing.
> If the value isn't used by the fragment program, what is the point in
computing it?
>
> 2) Consider the same fragment and vertex program if submitted by a client
> program (rather than generated by Mesa). They would be valid programs and
> definitely should not cause the driver to lock up.
>
> The link between VERT_ATTRIB_TEX0 and and texture unit 0 is only historical,
> there's nothing that says a fragment program will use that value as a texture
> coordinate or not - forcing it to be computed just because texture unit 0 is
> enabled doesn't really make sense.
Agreed.
It seems that this was caused by having zero interpolators.
> Is the fragment program one supplied by the user, or is it generated by
> texenvprogram.c?
By texenvprogram.c .
> What is the problem with col0?
I have to check this again on rv350 as it seems r480 can handle this.
Ill have to hack this at the backend if it doesnt work...
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
-------------------------------------------------------
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
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel