| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
If we can't fit all the VS outputs into the MRF, we need to overflow into
temporary GRF registers, then use some MOVs and a second brw_urb_WRITE()
instruction to place the overflow vertex results into the URB.
This is hit when a vertex/fragment shader pair has a large number of varying
variables (12 or more).
There's still something broken here, but it seems close...
|
| |
|
|
|
|
|
| |
Make the use_const_buffer field per-program and only call the code which
updates the constant buffer's data if the flag is set.
This should undo the perf regression from 20f3497e4b6756e330f7b3f54e8acaa1d6c92052
|
| |
|
|
|
|
| |
Hook up a constant buffer, binding table, etc for the VS unit.
This will allow using large constant buffers with vertex shaders.
The new code is disabled at this time (use_const_buffer=FALSE).
|
| | |
|
| |
|
|
|
|
|
|
| |
The i965 driver previously had it's own set of code to convert
fixed-function TNL state to a vertex program. Core Mesa has code to
do this, so there is no reason to duplicate that effort in the driver.
In fact, this duplication leads to bugs when other aspects of the Mesa
infrastructure change.
|
| |\
| |
| |
| |
| |
| |
| | |
Conflicts:
src/mesa/drivers/dri/i965/brw_sf.h
src/mesa/drivers/dri/i965/intel_context.c
|
| | |
| |
| |
| | |
most of the sample working with some small modification
|
| | |
| |
| |
| | |
else instruction fix.
|
| | | |
|
| |/
|
|
| |
eg: #include "shader/program.h" and remove -I$(TOP)/src/mesa/program
|
| | |
|
|
|
This driver comes from Tungsten Graphics, with a few further modifications by
Intel.
|
