Micha? Król wrote:
Hello,
Tomorrow I am going to make changes
that will affect drivers too.
The _TNL_ATTRIB_* 32-bit space has been
exhausted after adding 16 new vertex shader
attributes that cannot alias conventional ones.
Doing so, the TNLcontext::render_inputs will
be renamed to render_inputs_bitset[].
The name of SScontext::last_index will change
too. From now on this fields will be handled with
special macros, so if in the future we have
another 32-bit exhaustion, this will be handled
transparently.
I never touched drivers area, so the question is.
Should I try to make changes to them to prevent
compilation breaks or leave it to individual parties
and only send a how-to to them?
The way this has been done before is that you should ensure that the
drivers (especially the DRI drivers) at least compile with your changes,
and you should do your very best to ensure that your changes do the
right thing...
Before you commit anything, please post a debugged patch for review.
Can you manage that?
Does anyone not feel that this is still a reasonable way to do things?
Keith
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
