[Mesa-dev] cairo as state tracker

[Ilia Mirkin]

The idea is that gallium is an unstable unversioned API, and if you want
something else, then you make a state tracker which exposes a stable API.
This can be an API for which there is a preexisting standard, like va-api
or vdpau, or it can be one of your own creation which is consumed by some
other project. I don't think that you will find much support for
stabilizing and exporting the gallium API directly.

On Aug 4, 2016 23:48, "Enrico Weigelt, metux IT consult" <
enrico.weigelt at gr13.net> wrote:

> Hi folks,
>
>
> I'd like to get the cairo's gallium backend running again (hasn't been
> maintained for a long time and doesn't fit at all to recent mesa).
>
> The main problem I've got here is that gallium API is mesa-internal,
> so I'd like to do some steps on making it (semi-)public. I'm aware that
> it's still in flux, so we'll have an strict version dependency for
> quite some time - but I can live with that for now.
>
> I haven't yet understood, how to the different pieces work together,
> so any help is greatly appreciated.
>
> Let's start w/ a simple DRM usecase (no X involved). The big steps
> would IMHO be:
> #1: open the DRM device, setup fb and crtc
> #2: map a framebuffer (in the first steps I'd like to use cairo's
>     image surface - IOW: softraster - and later move to gallium
>     operations step by step)
> #2: initialize the GPU driver
> #3: start sending some render commands to the GPU.
>
> Maybe someone could give me some hints on how these things actually
> could look like ?
>
>
> --mtx
> _______________________________________________
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/mesa-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20160805/e4073f9c/attachment.html>