| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
| |
It is no longer needed since the new drm api code,
and it incorrectly checked if the buffer where there
for testing completeness when it should have checked
the texture instead.
|
| |
|
|
|
|
|
|
|
| |
Nasty bug when the surface is freed and another is allocated right on
top of it. The next time we set the fb state SP thinks it's the same
surface and doesn't flush, and when the flush eventually happens the
surface belongs to a completely different texture.
|
| |
|
|
|
|
| |
also enable cube/3d bits in txformat reg
|
|
|
|
|
| |
No point passing things twice here, also allows more state
to be setup properly.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Its not like it works well on 1.3 so may as well reach for greater
heights.
Signed-off-by: Dave Airlie <[email protected]>
|
| |
|
|
|
|
| |
pitch is pixels - 1, not bytes.
|
|\
| |
| |
| |
| | |
Conflicts:
src/mesa/shader/program_parse.tab.c
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
src/mesa/shader/lex.yy.c
src/mesa/shader/program_parse.tab.c
src/mesa/shader/program_parse.tab.h
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conditional write masks and the condition-code based KIL instruction
are all supported. The specific behavior of KIL in the following
shader may or may not match the behavior of other implementations:
!!ARBfp1.0
TEMP GT;
MOVC GT, fragment.texcoord[0];
KIL GT.x;
END
Should be it interpreted as 'KIL srcReg' or as 'KIL ccTest'? The
current parser will interpret it as 'KIL srcReg'.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
The lexer will return IDENTIFIER only when the name does not have an
associated symbol. Otherwise USED_IDENTIFIER is returned.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Adds support for declaring TEMP and OUTPUT variables as 'LONG' or
'SHORT' precision. The precision specifiers are parsed, but they are
currently ignored. Some support for this may be added in the future,
but neither Intel hardware nor, as far as I'm aware, Radeon hardware
support multiple precisions.
Also adds support for instruction precision ('X', 'H', and 'R')
suffixes and instruction condition code output ('C') suffix. This
results in a fairly major change to the lexer. Instructions are
matched with all the possible suffix strings. The suffix string are
then carved off by a context (i.e., which program mode and options are
set) aware parser that converts the suffixes to bits in
prog_instruction.
This could have been handled in the same way _SAT was originally
handled in the lexer, but it would have resulted in a very large lexer
with lots of opportunity for cut-and-paste errors.
|
| | |
| | |
| | |
| | |
| | | |
The new constructor copies fields from the prog_instruction that the
parser expects the lexer to set.
|
| | | |
|
| | |
| | |
| | |
| | | |
At this point the extension is not fully implemented.
|
| | |
| | |
| | |
| | |
| | |
| | | |
ARBfp requires scalar constants have a '.x' suffix, but NVfp_option
does not. This shows up with instructions that require a scalar
parameter (e.g., COS).
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
These seem to work well enough now with the new code. Composite acceleration
isn't quite there yet and thus remains disabled in xorg_composite_bind_state()
for now.
|
| | |
| | |
| | |
| | | |
operations.
|
| | | |
|
| | |
| | |
| | |
| | | |
gcc complained about a missing initializer.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Check that the formats are supported, and don't crash with source-only
pictures.
|
| | |
| | |
| | |
| | | |
Seems to work better for Composite acceleration.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
See xserver/render/picture.c:createSourcePicture(). This both simplifies the
code and avoids a crash because pFormat is NULL.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
src/mesa/drivers/dri/intel/intel_clear.c
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This fixes the clears in openarena with the new metaops clear code, and
the new piglit vbo-subdata-sync test.
Bug #23857.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Its flagging of extra state that's already flagged by the vtbl new_batch
when appropriate was confusing my tracking down of the OA clear bug.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
If you e.g. only need alpha, it ends up in the first reg,
not the last, as it would when reading rgb too.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Until now, only primitives wholly outside the view volume
were not drawn.
This was only visibile when using a viewport smaller than
the window size, naturally.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Separated the integer rounding mode flag for cvt.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
There's a good chance a loop won't execute correctly
though since our TEMP allocation assumes programs to
be executed linearly. Will fix later.
|