Age | Commit message (Collapse) | Author |
|
Once the clipping distance is calculated and stored per vertex, the
distances can be re-used when clipping is actually performed. This
doesn't have any immediate benefit, but it paves the way for
implementing gl_ClipDistance in vertex shaders and result.clip[] in
vertex programs.
This has not produces any oglconform regressions on my G31 system
which uses software TNL.
Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
Reviewed-by: Brian Paul <brianp@vmware.com>
|
|
|
|
Add _eglSetLogger and _eglSetLogLevel to allow drivers to change the
message logger or report level.
Signed-off-by: Chia-I Wu <olvaffe@gmail.com>
|
|
As a result, EGL_NONE is no longer a valid client API. And it is
possible that no config supports the current bound API.
Signed-off-by: Chia-I Wu <olvaffe@gmail.com>
|
|
Signed-off-by: Chia-I Wu <olvaffe@gmail.com>
|
|
eglGetProcAddress may not be used to query core (non-extension)
functions.
Signed-off-by: Chia-I Wu <olvaffe@gmail.com>
|
|
This allows an EGL driver to be compiled together with libEGL.so. It
eliminates the need to specify a driver, or support module loading on
new platforms.
Signed-off-by: Chia-I Wu <olvaffe@gmail.com>
|
|
gradients are supported, but not enabled by default due to little
testing they got
|
|
Need to restore code that fixed up the intel_texture_image state.
|
|
src in mask was broken
|
|
|
|
We need to check that we can actually render to the texture's format
before doing mipmap generation.
This may fix bug 24219.
|
|
|
|
It gets really annoying watching r300g tell me how it's filling surfaces.
Or falling back during filling surfaces.
|
|
Still not sure why st keeps handing down things we can't render to.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is mainly just to silence some warnings.
|
|
|
|
This lets us get rid of intel_miptree_depth_offsets() and simplify all
of the calling code.
|
|
|
|
|
|
|
|
need this to properly test with piglit/glean vert/fragprog tests
copied mostly from r300, many thanks to osiris, nha, airlied, others...
|
|
seems I overlooked this when removing hardcoded swizzles for this
one previously
|
|
|
|
|
|
extract all the rendering code to xorg_rendedrer, make both exa and xv
share that code. in the process cleanup the rendering code and implement
a lot more of the xv infrastructure.
|
|
|
|
|
|
Again, last valid address, not first invalid address. Fixes regression
in 255e5be265133280293bbfd8b2f9b74b2dec50bb that the kernel now catches
and caused piglit draw_elements_base_vertex to fail.
|
|
It's the address of the last valid byte, not the address of the first
invalid byte.
This should also fix problems with rendering with the new sanity checks in
the kernel.
|
|
Signed-off-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
this makes the default state same as r300
|
|
|
|
This is part of the fix for bug 24401.
|
|
This change silenced valgrind warnings but broke progs/tests/drawbuffers.
The problem is we don't know the surface's state when we start caching it
(it may or may not be initialized/cleared/etc). So "clearing" it here was
presumptuous. Leaving the code in place (but disabled) for reference and
when using valgrind.
Fixes bug 24401
|
|
|
|
fixes fdo bug 24248
|
|
Fixes bug 24426 for gallium.
|
|
Fixes bug 24426.
|
|
_ActualFormat is replaced by Format (MESA_FORMAT_x).
ColorEncoding, ComponentType, RedBits, GreenBits, BlueBits, etc. are
all replaced by MESA_FORMAT_x queries.
|
|
|
|
Change the fallback debugging around a bit and do the old commit correctly
|
|
This commit included a change that should have been in
its own commit, and turns out that you can do what was
suposed to go in it in much better way as well.
This reverts commit 5080e8bea6ae5cdb116023a5e2d8dbbb762bd69d.
|
|
|