(In reply to comment #19)
> The original bug of not supporting a framebuffer larger than 2048x2048 for i915
> class hardware has been fixed. The remaining bug that compiz does not respect
> the maximum renderbuffer and texture size of 2048 and gracefully fallback to
> metacity is a bug in compiz. i915 hardware can only support a maximum size of
> 2048 in the 3D pipeline, so attempting to use a GL compositor above such a size
> is futile.
This bug was about using compiz AT the maximum size - 2048 width, NOT ABOVE.
At the maximum size of texture (for example 2048x768) the screen was black (blank).
Compiz should drop at >2048, and all the time it did.
I have the feeling you just want to close this bug, without fixing...
I'll bet my shorts, that the same situation will happen at 4096 (i965) or 8192 (newer cards).
(In reply to comment #19)
> The original bug of not supporting a framebuffer larger than 2048x2048 for i915
> class hardware has been fixed. The remaining bug that compiz does not respect
> the maximum renderbuffer and texture size of 2048 and gracefully fallback to
> metacity is a bug in compiz. i915 hardware can only support a maximum size of
> 2048 in the 3D pipeline, so attempting to use a GL compositor above such a size
> is futile.
This bug was about using compiz AT the maximum size - 2048 width, NOT ABOVE.
At the maximum size of texture (for example 2048x768) the screen was black (blank).
Compiz should drop at >2048, and all the time it did.
I have the feeling you just want to close this bug, without fixing...
I'll bet my shorts, that the same situation will happen at 4096 (i965) or 8192 (newer cards).