| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Reviewed-by: José Fonseca <[email protected]>
Reviewed-by: Eric Anholt <[email protected]>
|
|
|
|
|
| |
Reviewed-by: José Fonseca <[email protected]>
Reviewed-by: Eric Anholt <[email protected]>
|
|
|
|
|
| |
Reviewed-by: José Fonseca <[email protected]>
Reviewed-by: Eric Anholt <[email protected]>
|
|
|
|
|
| |
Reviewed-by: José Fonseca <[email protected]>
Reviewed-by: Eric Anholt <[email protected]>
|
|
|
|
|
|
|
| |
They're no longer used anywhere.
Reviewed-by: José Fonseca <[email protected]>
Reviewed-by: Eric Anholt <[email protected]>
|
|
|
|
|
| |
Reviewed-by: José Fonseca <[email protected]>
Reviewed-by: Eric Anholt <[email protected]>
|
|
|
|
|
|
|
| |
Another step toward removing the _DD_NEW_x flags
Reviewed-by: José Fonseca <[email protected]>
Reviewed-by: Eric Anholt <[email protected]>
|
|
|
|
|
|
|
|
| |
This will replace the soon-to-be-removed _DD_NEW_SEPARATE_SPECULAR flag.
Note: there's a similar composite _MESA_NEW_NEED_EYE_COORDS flag set already.
Reviewed-by: José Fonseca <[email protected]>
Reviewed-by: Eric Anholt <[email protected]>
|
|
|
|
|
|
|
|
| |
Just use the corresponding _NEW_x flags intead. The _DD_NEW_x flags
will be removed in a following patch.
Reviewed-by: José Fonseca <[email protected]>
Reviewed-by: Eric Anholt <[email protected]>
|
|
|
|
|
|
|
| |
The driver Clear() function should just grab the clear color out of the
context.
Reviewed-by: Dave Airlie <[email protected]>
|
|
|
|
|
|
| |
Setup the clearing color in the clear() function.
Reviewed-by: Dave Airlie <[email protected]>
|
|
|
|
|
|
| |
Just setup the clearing color in clear_buffers().
Reviewed-by: Dave Airlie <[email protected]>
|
|
|
|
|
|
| |
The state.color.clear value was never used anywhere.
Reviewed-by: Dave Airlie <[email protected]>
|
|
|
|
|
|
|
| |
Not used by any drivers. Drivers can easily access the values
from the Mesa context at glClear() time.
Reviewed-by: Dave Airlie <[email protected]>
|
|
|
|
|
|
|
| |
The computed stencil.clear and depth.clear values aren't used anywhere.
Those fields have been removed too.
Reviewed-by: Dave Airlie <[email protected]>
|
|
|
|
|
|
| |
The flags which were computed were never actually used.
Reviewed-by: Dave Airlie <[email protected]>
|
|
|
|
| |
Fixes scons build.
|
|
|
|
|
|
|
|
|
| |
Set the close on exec flag when opening dri character devices, so they
will be closed and free any resouces allocated in exec.
Signed-off-by: David Fries <[email protected]>
Reviewed-by: Adam Jackson <[email protected]>
Signed-off-by: Dave Airlie <[email protected]>
|
|
|
|
|
|
| |
Necessary to prevent type mismatches on MinGW.
Signed-off-by: Dave Airlie <[email protected]>
|
|
|
|
| |
Signed-off-by: Dave Airlie <[email protected]>
|
|
|
|
|
|
|
|
| |
This issue might recur on other OSes. If so then it might be better
to remove the C-preprocessor magic, and use fully qualified defines
instead.
Signed-off-by: Dave Airlie <[email protected]>
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Store client-defined message IDs in a hash table,
and sort them by severity into three linked lists
so they can be selected by severity level later.
|
|
|
|
| |
The final piece of the puzzle for GL_ARB_debug_output.
|
|
|
|
|
|
|
|
|
| |
This state is needed for deciding whether or not to log
application messages with IDs that haven't been specifically
passed to glDebugMessageControlARB yet.
State for each individual ID number ever passed to
glDebugMessageControlARB (per-context) still needs to be added.
|
| |
|
|
|
|
|
| |
Controlling the output of client-provided messages
isn't done yet.
|
| |
|
| |
|
|
|
|
| |
Marek v2: don't add the extension to extensions.c yet
|
| |
|
|
|
|
| |
Marek v2: replace GLDEBUGPROCARB with void*
|
|
|
|
| |
Also add _mesa_vsnprintf.
|
|
|
|
|
|
|
|
|
| |
Unfortunately, Unigine Heaven 3.0 still needs this.
NOTE: This is a candidate for the 8.0 branch.
Signed-off-by: Kenneth Graunke <[email protected]>
Reviewed-by: Eric Anholt <[email protected]>
|
|
|
|
|
|
|
| |
min_index/max_index are merely conservative guesses, so we can't
make buffer overflow detection based on their values.
Tested-by: Jakob Bornecrantz <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are several cases in which we need to explicity "rebase" colors
(ex: set G=B=0) when getting GL_LUMINANCE textures:
1. If the luminance texture is actually stored as rgba
2. If getting a luminance texture, but returning rgba
3. If getting an rgba texture, but returning luminance
Fixes https://bugs.freedesktop.org/show_bug.cgi?id=46679
Also fixes the new piglit getteximage-luminance test.
Reviewed-by: José Fonseca <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Based on a patch submitted by Vic Lee. The other part of his patch
which checked the fs pointer wasn't needed.
This fixes a crash when clear() is called before any VS or FS is set.
But this can only happen when the driver is used without the Mesa
state tracker.
NOTE: This is a candidate for the 8.0 branch.
Reviewed-by: José Fonseca <[email protected]>
|
| |
|
| |
|
|
|
|
|
|
| |
This fixes a crash in XBMC, but we still doesn't see a picture.
Signed-off-by: Christian König <[email protected]>
|
|
|
|
|
|
| |
Just another xine workaround.
Signed-off-by: Christian König <[email protected]>
|
|
|
|
| |
Signed-off-by: Christian König <[email protected]>
|
|
|
|
|
|
|
| |
For reasons I don't understand xine tries to set
the surface format by using a zero pitch.
Signed-off-by: Christian König <[email protected]>
|
|
|
|
|
|
|
|
|
|
| |
This gets xine working with VDPAU.
v2: some minor bugfixes.
v3: create the resource with the subsampled
format to avoid tilling problems
Signed-off-by: Christian König <[email protected]>
|
|
|
|
|
|
| |
v2: r600 formats are msb first!
Signed-off-by: Christian König <[email protected]>
|
|
|
|
|
|
| |
Just to keep lp_test_format happy.
Signed-off-by: Christian König <[email protected]>
|
|
|
|
|
|
|
| |
v2: simplify implementation by using correct swizzle
v3: fix mix with successor patch
Signed-off-by: Christian König <[email protected]>
|
|
|
|
| |
Signed-off-by: Christian König <[email protected]>
|