Displaying 3 results from an estimated 3 matches for "nouveau_check_framebuffer_complet".
Did you mean:
nouveau_check_framebuffer_complete
2014 Jan 15
1
[PATCH v2] nouveau: add framebuffer validation callback
...xObject);
}
+static int
+validate_format_bpp(gl_format format)
+{
+ switch (format) {
+ case MESA_FORMAT_XRGB8888:
+ case MESA_FORMAT_ARGB8888:
+ case MESA_FORMAT_Z24_S8:
+ return 32;
+ case MESA_FORMAT_RGB565:
+ case MESA_FORMAT_Z16:
+ return 16;
+ default:
+ return 0;
+ }
+}
+
+static void
+nouveau_check_framebuffer_complete(struct gl_context *ctx,
+ struct gl_framebuffer *fb)
+{
+ const struct nouveau_driver *drv = context_drv(ctx);
+ struct gl_renderbuffer_attachment *color =
+ &fb->Attachment[BUFFER_COLOR0];
+ struct gl_renderbuffer_attachment *depth =
+ &fb->Attachment[BUFFER_DEPTH];
+ int co...
2014 Jan 10
2
[PATCH] nouveau: add framebuffer validation callback
Fixes assertions when trying to attach textures to fbs with formats not
supported by the render engines.
See https://bugs.freedesktop.org/show_bug.cgi?id=73459
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>
---
In a perfect world I'd have separate callbacks for depth and color, but given
the list of supported values, I don't think this matters. Also I used
2014 Jan 14
0
[PATCH] nouveau: add framebuffer validation callback
...e screen.
>
That's called before any rendering happens to check if we need to renew
any of the render buffers, e.g. in case the window was resized or
SwapBuffers() was called. It's rather unfortunate that the name of your
new function is just a permutation of the old one, how about
'nouveau_check_framebuffer_completeness'?
> src/mesa/drivers/dri/nouveau/nouveau_driver.h | 1 +
> src/mesa/drivers/dri/nouveau/nouveau_fbo.c | 38 +++++++++++++++++++++++++++
> src/mesa/drivers/dri/nouveau/nv04_context.c | 14 ++++++++++
> src/mesa/drivers/dri/nouveau/nv10_context.c | 16 +++++++++++
>...