| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Generating mipmaps finally works, among other things. Yay!
|
| |
|
|
|
|
|
| |
Unfortunately we can't fix this easily in the R300 fragment shader,
and it's probably not worth the effort.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In particular, gcc man page warns that
union a_union {
int i;
double d;
};
int f() {
double d = 3.0;
return ((union a_union *) &d)->i;
}
"might" not be ok (why not?), even though it doesn't seem to generate
any warnings. Hence don't use this and do the extra step to actually use
assignment to get the values in/out of the union.
This changes parts of 3456f9149b3009fcfce80054759d05883d3c4ee5.
|
| |
| |
| |
| |
| |
| |
| |
| | |
use pointer to union instead of void pointer.
gcc complained a lot, depending what the pointer originally actually was.
Looks like it's in fact maybe legal to cast for instance uint pointers to
union pointers as long as union contains a uint type, hence use this with some
callers, other just use union util_color in the first place.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
Conflicts:
src/mesa/drivers/dri/r600/r700_assembler.c
src/mesa/main/version.h
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
progs/demos/projtex.c
progs/xdemos/glxinfo.c
src/mesa/main/version.h
To fix the confilicts in projtex.c and glxinfo.c I just took the code from
mesa_7_6_branch. The conflicts seem to have occured from cherry-picks from
mesa_7_7_branch to mesa_7_6_branch followed by commmits just to
mesa_7_6_branch.
|
| | | |
| | | |
| | | |
| | | | |
Fixes bug 24501
|
| | | |
| | | |
| | | |
| | | |
| | | | |
If *I* can't read it, there's a strong possibility others can't,
either.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Otherwise a CS is refused by kernel 2.6.31 (and maybe all later
versions, not sure).
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Just make it cover the whole framebuffer in that case. Otherwise the kernel CS
checker may complain, e.g. running progs/demos/gearbox. That runs fast now
here, but doesn't look right yet.
|
| | | |
| | | |
| | | |
| | | | |
Also, overlapping occlusion queries seems to work now.
|
| | | | |
|
| | | | |
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | | |
Conflicts:
src/gallium/state_trackers/xorg/xorg_exa.c
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
There's like five good reasons for this, I swear.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
src/gallium/drivers/r300/r300_vs.c
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
SrcRegister -> Register
SrcRegisterInd -> Indirect
SrcRegisterDim -> Dimension
SrcRegisterDimInd -> DimIndirect
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
DstRegister -> Register
DstRegisterInd -> Indirect
|
| | | | |
| | | | |
| | | | |
| | | | | |
DeclarationRange -> Range
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
InstructionPredicate -> Predicate
InstructionLabel -> Label
InstructionTexture -> Texture
FullSrcRegisters -> Src
FullDstRegisters -> Dst
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Rename Semantic.SemanticName to Semantic.Name. Similar for
SemanticIndex, and the members of the tgsi_version struct.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It would be nice if these drivers built under the linux-debug header
so that these types of interface changes can be minimally propogated
into those drivers by people without the hardware. They don't have to
generate a working driver -- though a command-dumping winsys would be
an excellent for regression checking.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
No need to parse TGSI tokens since it's easier to walk through shader
semantics.
Also fog coordinates now work reliably.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The state setups which aren't derived anymore have been moved to the VS
and FS objects.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Now it always correctly pairs up VS and FS even if the semantics and indices
of VS outputs and FS inputs don't match.
|
| | | | | |
|
| |/ / /
|/| | | |
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
src/gallium/drivers/r300/r300_texture.c
src/gallium/state_trackers/xorg/xorg_exa.c
src/mesa/state_tracker/st_cb_texture.c
|
| |/ /
| | |
| | |
| | | |
width/height/depth arrays
|
| | | |
|
| | |
| | |
| | |
| | | |
Oops.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Instead of vs_tab, we use vs_output_tab and it's local now. fs_tab hasn't
been used anywhere, so I removed it and r300_update_fs_tab too.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
And reorder fragment shader inputs so that the colors are before texcoords,
as is allocated by the shader compiler. This commit makes VS->FS attribute
routing work on R500.
|
| | |
| | |
| | |
| | |
| | | |
We must update PSC when we change the vertex format, e.g. vertex colors
from RGBA to BGRA.
|
| | |
| | |
| | |
| | |
| | |
| | | |
These now work:
piglit/lodclamp
piglit/levelclamp
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This patch removes draw_context entirely from the HW TCL path and cleans up
a few other things along the way. Hopefully, nothing got broken.
Thanks to Marek Olšák for testing, review, and pointing out my bugs. :3
|
| | |
| | |
| | |
| | | |
Previously, this reg wasn't emitted at all if texture_count == 0.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
(0, 0, 0, 1) is a much saner default value, and texrect factors only need
to be (1/s, 1/t, 0, 1).
|