diff options
| author | Christoph Bumiller <[email protected]> | 2011-01-23 21:29:30 +0100 |
|---|---|---|
| committer | Christoph Bumiller <[email protected]> | 2011-01-23 21:35:27 +0100 |
| commit | a287a758c6567405a7ea10df21e586d1e2ff08ec (patch) | |
| tree | a06f473b7558331d6c54c18ad208cd4f86f5a8b8 /configs/bluegene-osmesa | |
| parent | f154cd231552d16c66b87ca1e32be5451f6bdae4 (diff) | |
nvc0: implement point coord replacement
But we have to cheat and peek at the GENERIC semantic indices the
state tracker uses for TEXn.
Only outputs from 0x300 to 0x37c can be replaced, and so we have to
know on shader compilation which ones to put there in order to keep
doing separate shader objects properly.
At some point I'll probably create a patch that makes gallium not
force us to discard the information about what is a TexCoord.
Diffstat (limited to 'configs/bluegene-osmesa')
0 files changed, 0 insertions, 0 deletions