diff options
author | Ian Romanick <[email protected]> | 2012-02-01 10:18:13 -0700 |
---|---|---|
committer | Ian Romanick <[email protected]> | 2012-02-03 10:50:01 -0700 |
commit | 87b4c9b322dabeba7c9a9d02e9efefd2c89e6625 (patch) | |
tree | 58fec8ab42faddf811818ad97efa759b9a5e08e3 /include/c99 | |
parent | 0fcc518964223d9baaa2b45e80afeb800beb872f (diff) |
intel: FBOs with texture border are unsupported
FBOs differ from textures in a significant way. With textures, we can
strip the border and get correct rendering except when the application
fetches texels outside [0,1].
With an FBO, the pixel at (0,0) is in the border. The
ARB_framebuffer_object spec says:
"If the attached image is a texture image, then the window
coordinates (x[w], y[w]) correspond to the texel (i, j, k), from
figure 3.10 as follows:
i = (x[w] - b)
j = (y[w] - b)
k = (layer - b)
where <b> is the texture image's border width..."
Since the border doesn't exist, we can never render any pixels in the
correct location. Just mark these FBOs FRAMEBUFFER_UNSUPPORTED.
NOTE: This is a candidate for the 8.0 branch.
Signed-off-by: Ian Romanick <[email protected]>
Reviewed-by: Kenneth Graunke <[email protected]>
Reviewed-by: Eric Anholt <[email protected]>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=42336
Diffstat (limited to 'include/c99')
0 files changed, 0 insertions, 0 deletions