EGL/GLES with Linux Framebuffer

[Jasbir]

I have seen some threads which lightly touch on the subject of the framebuffer support and unfortunately I'm still unclear about the ozone design.

If my device has no drm/kms support but supports rendering through egl/gles to a framebuffer (/dev/fb0). Is it the responsibility of OzonePlatform to return a valid NativeDisplayType/NativeWindowType or just a file handle to the frame buffer? I presume SurfaceFactoryOzone would be responsible for creating a surface (EGLSurface). What's also not clear is who is  responsible for a redraw (eglSwapBuffers) ?

[Michael Spang]

On Dec 23, 2014 2:51 AM, "Jasbir" <jasb...@gmail.com> wrote:
>
> I have seen some threads which lightly touch on the subject of the framebuffer support and unfortunately I'm still unclear about the ozone design.
>
> If my device has no drm/kms support but supports rendering through egl/gles to a framebuffer (/dev/fb0). Is it the responsibility of OzonePlatform to return a valid NativeDisplayType/NativeWindowType or just a file handle to the frame buffer?

The former.

> I presume SurfaceFactoryOzone would be responsible for creating a surface (EGLSurface).

Not quite... this class is indirectly responsible for creating (or providing) the EGLNativeWindow. The EGLSurface itself is created from ui/gl/gl_surface_ozone.cc.

> What's also not clear is who is  responsible for a redraw (eglSwapBuffers) ?

The compositor is responsible for driving this. The platform only provides vsync timing information to help inform the compositor scheduling.

Michael