DRI2 Protocol Spec Draft
michel at tungstengraphics.com
Tue Sep 9 04:27:14 PDT 2008
On Mon, 2008-09-08 at 17:58 -0400, Kristian Høgsberg wrote:
> Keith talked me intro writing a spec for DRI2, which I grudgingly must
> admit is a good idea. I used the randr spec as a template, except I
> replaced the flowery section dividers with a more fitting gears motif.
> It's still a work in progress, mostly the introductory/background
> sections though. The requests and wire encoding sections are mostly
> complete and is close to what's in the git repos at this point. The
> implementation isn't fully uptodate with the spec yet, but I figured
> it would be wise to circulate the spec before doing more code churn,
> so here it is.
I think it'd be good if the authentication stuff could be made/kept
optional or at least not DRM specific. (I'm not sure GEM or the DRM in
general is within scope of this spec at all)
I do wonder if DRI2GetBuffers should return the drawable position
relative to the origin of each buffer... guess it isn't strictly
necessary except maybe for the real frontbuffer.
For DRI2CopyRegion, you're leaving it to the DDX driver to pick the CRTC
to synchronize to? I'm not sure that'll work too well with overlapping
viewports, where the user may want to choose which CRTC to synchronize
to for each application. This request also still seems to be missing
return values for the sequence number when the copy is expected to take
place and tokens for synchronization of direct rendering to the
source/destination buffer. Oh, and I think it should take relative
sequence numbers as well as absolute ones.
Should 10.2 say DRI2_BUFFER_BACK_LEFT rather than
P.S. Does the author of
deserve an acknowledgement as well? ;)
Earthling Michel Dänzer | http://tungstengraphics.com
Libre software enthusiast | Debian, X and DRI developer
More information about the xorg