diff options
| author | Eric Anholt <[email protected]> | 2013-06-06 11:13:02 -0700 |
|---|---|---|
| committer | Eric Anholt <[email protected]> | 2013-06-07 16:05:42 -0700 |
| commit | 3c21a7d3c9b626a10a38987d77b9e77d70bd67d7 (patch) | |
| tree | 8136166c8b27222afca1fbf2518459c378eebecc /src/gallium/state_trackers | |
| parent | 9e3475b39ae34244045e0dcd6b98e1526c10c6bf (diff) | |
mesa: Report core FBO incompleteness cases through GL_ARB_debug_output.
Just like we produce from inside the Intel driver, this can help provide
information quickly about FBO incompatibility problems (particularly when
using apitrace replay).
Currently, in driver-marked incompleteness cases, you'll get both the
driver message and the core message on Intel. Until the other drivers are
fixed to produce output, I think this is better than not putting in a
message for driver-marked incomplete.
Reviewed-by: Brian Paul <[email protected]>
Diffstat (limited to 'src/gallium/state_trackers')
0 files changed, 0 insertions, 0 deletions