diff options
| author | Marek Olšák <[email protected]> | 2012-02-23 23:44:36 +0100 |
|---|---|---|
| committer | Marek Olšák <[email protected]> | 2012-02-27 02:03:23 +0100 |
| commit | 04e324008759282728a95a1394bac2c4c2a1a3f9 (patch) | |
| tree | 71691cd97f13431ca8ddb7c902638e5b775eac67 /src/gallium/drivers/nv50/nv50_screen.c | |
| parent | 74d303521e6ba41d1cbeb75edb2f834ebbe8c550 (diff) | |
gallium: remove PIPE_SHADER_CAP_OUTPUT_READ
r600g is the only driver which has made use of it. The reason the CAP was
added was to fix some piglit tests when the GLSL pass lower_output_reads
didn't exist.
However, not removing output reads breaks the fallback for glClampColorARB,
which assumes outputs are not readable. The fix would be non-trivial
and my personal preference is to remove the CAP, considering that reading
outputs is uncommon and that we can now use lower_output_reads to fix
the issue that the CAP was supposed to workaround in the first place.
Diffstat (limited to 'src/gallium/drivers/nv50/nv50_screen.c')
| -rw-r--r-- | src/gallium/drivers/nv50/nv50_screen.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/src/gallium/drivers/nv50/nv50_screen.c b/src/gallium/drivers/nv50/nv50_screen.c index 1d5359327bc..27566e24108 100644 --- a/src/gallium/drivers/nv50/nv50_screen.c +++ b/src/gallium/drivers/nv50/nv50_screen.c @@ -206,8 +206,6 @@ nv50_screen_get_shader_param(struct pipe_screen *pscreen, unsigned shader, return 0; case PIPE_SHADER_CAP_MAX_TEXTURE_SAMPLERS: return 32; - case PIPE_SHADER_CAP_OUTPUT_READ: - return 0; /* maybe support this for fragment shaders ? */ default: NOUVEAU_ERR("unknown PIPE_SHADER_CAP %d\n", param); return 0; |