Ok. I said that this bug doesnt exist and it was just my problem ...
I changed my mind as it appeared again after rebuilding just about
everything and tracked it down after long battle. This was caused by
missing curly braces around texcoord VAP input configuration and resulted
in all 8 texture units to be configured whenever vertex programs were
used.

However there is one thing I dont understand about this:
How did badly configuring VAP input caused vertex programs to get broken
when dummy var was added into struct r300_dma or struct r300_state ?

AFAIK, even if textures would be enabled for no reason there should be
enough checks in r300_setup_textures and other places not to cause bad
pointers to read from there.

There was a bug that could of caused this:
#define ALLOC_STATE( ATOM, CHK, SZ, NM, IDX )                           \
...
      r300->hw.ATOM.cmd = (uint32_t*)CALLOC(SZ * sizeof(uint32_t));     \
...
caller:
        ALLOC_STATE( tex.filter, variable, mtu+1, "tex_filter", 0 );
result:
      r300->hw.ATOM.cmd = (uint32_t*)CALLOC(mtu+1 * sizeof(uint32_t));  \

This have been fixed some time ago though.
Further more I modified verify_r300ResetHwState earlier to test that each
state atom can actually hold all data its ment to hold, so these type of
bugs should be gone.

Could it be because R300_MAX_AOS_ARRAYS is only 8 whereas 9 would of needed ?

Im not sure if trying to figure this out like this is worth the effort
though as we can probably figure out any outstanding problems with
textures by writing test programs.

Some shots:
http://nu.rasterburn.org/~aet/arbvptorus_1.png
http://nu.rasterburn.org/~aet/arbvptorus_2.png

-- 
Aapo Tahkola


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to