[Mesa-dev] mx6q: Cannot run Cinematic demo correctly
Fabio Estevam
festevam at gmail.com
Tue Mar 14 17:16:02 UTC 2017
Hi Otavio,
On Tue, Mar 14, 2017 at 1:58 PM, Otavio Salvador
<otavio.salvador at ossystems.com.br> wrote:
> On Tue, Mar 14, 2017 at 12:31 PM, Fabio Estevam <festevam at gmail.com> wrote:
> ...
>> The cover of the movies are just black rectangles instead of showing
>> the actual movie pictures.
> ...
>
> I am attaching the two patches I am applying on mesa locally and which
> has fixed our current issues.
Thanks for the patches!
By only reverting:
commit 6c89a728d9e5d072cb504453e73077564c6523d3
Author: Wladimir J. van der Laan <laanwj at gmail.com>
Date: Wed Dec 7 12:59:54 2016 +0000
etnaviv: Cannot render to rb-swapped formats
Exposing rb swapped (or other swizzled) formats for rendering would
involve swizzing in the pixel shader. This is not the case at the
moment, so reject requests for creating such surfaces.
(GPUs that need an extra resolve step anyway due to multiple pixel
pipes, such as gc2000, might also do this swap in the resolve operation.
But this would be tricky to keep track of)
CC: <mesa-stable at lists.freedesktop.org>
Signed-off-by: Wladimir J. van der Laan <laanwj at gmail.com>
Acked-by: Christian Gmeiner <christian.gmeiner at gmail.com>
I can confirm that the Cinematic demo can run successfully. I do not
see the black boxes, nor font issues anymore.
Also the previous error messages are gone:
QOpenGLFramebufferObject: Unsupported framebuffer format.
QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
QOpenGLFramebufferObject: Unsupported framebuffer format.
QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
QOpenGLFramebufferObject: Unsupported framebuffer format.
QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
QOpenGLFramebufferObject: Unsupported framebuffer format.
QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
as to your other patch: I do not see commit
89bb5c79e29613ad9a4e43d670654e98a220fc60 in mesa tree.
Wladimir/Christian,
What would be the proper fix for this problem?
Thanks
More information about the mesa-dev
mailing list