On Tue, Aug 9, 2016 at 8:11 AM, Enrico Weigelt, metux IT consult <
enrico.weig...@gr13.net> wrote:
> On 07.08.2016 12:50, Marek Olšák wrote:
>
> > It would mainly be a futile task if it had to compete with their
> > official Mesa driver.
>
> Not quite. Would give us all of gallium's capabilities a
On Tue, Aug 9, 2016 at 11:11 AM, Enrico Weigelt, metux IT consult
wrote:
> On 07.08.2016 12:50, Marek Olšák wrote:
>
>> It would mainly be a futile task if it had to compete with their
>> official Mesa driver.
>
> Not quite. Would give us all of gallium's capabilities also for
> the intel chips, f
On 07.08.2016 12:50, Marek Olšák wrote:
> It would mainly be a futile task if it had to compete with their
> official Mesa driver.
Not quite. Would give us all of gallium's capabilities also for
the intel chips, for example having lots of different state trackers.
(coming back to my original inte
On Sun, Aug 7, 2016 at 9:44 AM, Enrico Weigelt, metux IT consult
wrote:
> On 06.08.2016 19:17, Marek Olšák wrote:
>
>> The lack of interest from Intel is the main reason.
>
> And the other mesa folks also not interested ?
> Would an conversion to gallium be a very complex task ?
It would mainly b
On 06.08.2016 19:17, Marek Olšák wrote:
> The lack of interest from Intel is the main reason.
And the other mesa folks also not interested ?
Would an conversion to gallium be a very complex task ?
--mtx
___
mesa-dev mailing list
mesa-dev@lists.freede
On 06.08.2016 19:46, Emil Velikov wrote:
> You mentioned "cairo's gallium backend running again". Can you point
> to the said code ?
https://cgit.freedesktop.org/cairo/tree/src/drm/cairo-drm-gallium-surface.c
> Can you elaborate why you're thinking against having the cairo
> state-tracker in mes
On 6 August 2016 at 15:59, Enrico Weigelt, metux IT consult
wrote:
> On 06.08.2016 13:16, Nicolai Hähnle wrote:
>
>> Well, in your first mail it sounded like you wanted to stabilize the
>> Gallium API itself.
>
> Not actually stabilizing, but making it semi-public. (at dist level in
> an separate
On Sat, Aug 6, 2016 at 5:03 PM, Enrico Weigelt, metux IT consult
wrote:
> On 06.08.2016 15:23, Marek Olšák wrote:
>
>> I'd recommend moving the cairo rendering code into Mesa and have Mesa
>> implement and export some kind of a low-level cairo library.
>
> That would essentially create a circular
On 06.08.2016 15:23, Marek Olšák wrote:
> I'd recommend moving the cairo rendering code into Mesa and have Mesa
> implement and export some kind of a low-level cairo library.
That would essentially create a circular dependency - and cairo's
surface backend API is also private.
> Please note that
On 06.08.2016 13:16, Nicolai Hähnle wrote:
> Well, in your first mail it sounded like you wanted to stabilize the
> Gallium API itself.
Not actually stabilizing, but making it semi-public. (at dist level in
an separate package). Of course, external state trackers need to built
to the right galli
On Fri, Aug 5, 2016 at 6:48 AM, Enrico Weigelt, metux IT consult
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-inter
On 06.08.2016 10:49, Enrico Weigelt, metux IT consult wrote:
On 05.08.2016 17:36, Ilia Mirkin wrote:
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.
That's exactly what I intend: cario.
Well, i
On 05.08.2016 17:36, Ilia Mirkin wrote:
> 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.
That's exactly what I intend: cario.
--mtx
___
mesa-dev m
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
othe
On 05.08.2016 06:48, Enrico Weigelt, metux IT consult wrote:
... replying to myself... ;-o
> 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
If I'm correct, the first thing to do is to get a proper winsys, right ?
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 st
16 matches
Mail list logo
