2011/12/7 Michel Dänzer <[email protected]>:
> On Mit, 2011-12-07 at 09:20 +0000, Dave Airlie wrote:
>> 2011/12/7 Michel Dänzer <[email protected]>:
>> > On Mit, 2011-12-07 at 08:40 +0000, Dave Airlie wrote:
>> >> >
>> >> > I have a feeling, since dri2 is not strictly restricted to GLX, whether 
>> >> > this
>> >> > should really be
>> >> > implemented in the glx code before calling into dri2? Otoh that would 
>> >> > mean
>> >> > the server side
>> >> > would need to be able to handle the case anyway.
>> >>
>> >> The problem is that GLX doesn't get a chance, since the only place GLX
>> >> knows whether the drawable is window or pixmap is in the server, and
>> >> DRI2 protocol bypasses GLX to do this.
>> >>
>> >> So I'm not really sure how we can block that.
>> >
>> > The client-side GLX code currently can't tell apart pixmaps from
>> > windows, but is there no way it could?
>
> No answer?

This requires reading of code.

>
> Wrong for GLX, not obviously for DRI2.

Thats why I mentioned we could just do a DRI2 extension for non-GLX
DRI2, since DRI2 was originally meant for GLX use cases.


>> I don't care about broken GLX clients, I just care about making
>> non-broken ones work okay.
>
> Note that I'm referring to libGL. It just makes no sense for it to even
> call DRI2SwapBuffers in this case.

Indeed, but fixing it without invasive protocol work may be messy, but
I'm not really a GLX or DRI2 expert and its hard to fathom the
intentions of DRI2 original authors wrt this GLX case.

Dave.
_______________________________________________
mesa-dev mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Reply via email to