Re: DRI2 Protocol Spec Draft

2008-09-12 Thread Michel Dänzer
On Thu, 2008-09-11 at 11:59 -0400, Kristian Høgsberg wrote: > > > On Wed, 2008-09-10 at 14:16 -0400, Kristian Høgsberg wrote: > >> On Tue, Sep 9, 2008 at 1:34 PM, Michel Dänzer > >> <[EMAIL PROTECTED]> wrote: > >> > > >> > If the GLX implementation is to use DRI2CopyRegion for synchronization > >>

Re: DRI2 Protocol Spec Draft

2008-09-12 Thread Michel Dänzer
On Thu, 2008-09-11 at 16:02 -0400, Kristian Høgsberg wrote: > On Thu, Sep 11, 2008 at 3:49 PM, Jesse Barnes <[EMAIL PROTECTED]> wrote: > > On Thursday, September 11, 2008 8:59 am Kristian Høgsberg wrote: > >> On Thu, Sep 11, 2008 at 6:40 AM, Michel Dänzer > >> > >> <[EMAIL PROTECTED]> wrote: > >> >

Re: DRI2 Protocol Spec Draft

2008-09-11 Thread Srecko Morovic
Adam Jackson nwnk.net> writes: > > While true, there is exactly zero API in either of GL or Xv for > specifying which CRTC to sync to if there's a choice. Adding this to > DRI2 before having any way for a real rendering layer to consume it > seems like gratuitous overdesign. > Btw. maybe this

Re: DRI2 Protocol Spec Draft

2008-09-11 Thread Kristian Høgsberg
On Thu, Sep 11, 2008 at 3:49 PM, Jesse Barnes <[EMAIL PROTECTED]> wrote: > On Thursday, September 11, 2008 8:59 am Kristian Høgsberg wrote: >> On Thu, Sep 11, 2008 at 6:40 AM, Michel Dänzer >> >> <[EMAIL PROTECTED]> wrote: >> > On Wed, 2008-09-10 at 14:09 -0400, Kristian Høgsberg wrote: >> >> On Tu

Re: DRI2 Protocol Spec Draft

2008-09-11 Thread Jesse Barnes
On Thursday, September 11, 2008 8:59 am Kristian Høgsberg wrote: > On Thu, Sep 11, 2008 at 6:40 AM, Michel Dänzer > > <[EMAIL PROTECTED]> wrote: > > On Wed, 2008-09-10 at 14:09 -0400, Kristian Høgsberg wrote: > >> On Tue, Sep 9, 2008 at 11:46 AM, Keith Packard <[EMAIL PROTECTED]> wrote: > >> > On T

Re: DRI2 Protocol Spec Draft

2008-09-11 Thread Adam Jackson
On Thu, 2008-09-11 at 18:18 +0200, Xavier Bestel wrote: > On Thu, 2008-09-11 at 11:59 -0400, Kristian Høgsberg wrote: > > We can then add the CRTC to sync to as an argument > > later if we find a case where the client really can make a better > > decision than the server. > > I can think of such

Re: DRI2 Protocol Spec Draft

2008-09-11 Thread Xavier Bestel
On Thu, 2008-09-11 at 11:59 -0400, Kristian Høgsberg wrote: > We can then add the CRTC to sync to as an argument > later if we find a case where the client really can make a better > decision than the server. I can think of such an imaginary case: imagine an NLE (video editor) which only cares ab

Re: DRI2 Protocol Spec Draft

2008-09-11 Thread Kristian Høgsberg
On Thu, Sep 11, 2008 at 6:40 AM, Michel Dänzer <[EMAIL PROTECTED]> wrote: > On Wed, 2008-09-10 at 14:09 -0400, Kristian Høgsberg wrote: >> On Tue, Sep 9, 2008 at 11:46 AM, Keith Packard <[EMAIL PROTECTED]> wrote: >> > On Tue, 2008-09-09 at 13:27 +0200, Michel Dänzer wrote: >> > >> >> For DRI2CopyRe

Re: DRI2 Protocol Spec Draft

2008-09-11 Thread Michel Dänzer
On Wed, 2008-09-10 at 14:09 -0400, Kristian Høgsberg wrote: > On Tue, Sep 9, 2008 at 11:46 AM, Keith Packard <[EMAIL PROTECTED]> wrote: > > On Tue, 2008-09-09 at 13:27 +0200, Michel Dänzer wrote: > > > >> For DRI2CopyRegion, you're leaving it to the DDX driver to pick the CRTC > >> to synchronize t

Re: DRI2 Protocol Spec Draft

2008-09-10 Thread Keith Packard
On Wed, 2008-09-10 at 17:28 -0400, Kristian Høgsberg wrote: > No that's why the existing scheme is better, it doesn't rely on > random/cryptographical tokens. It just needs to be a unique handle > that lets the server identify the right client to authenticate. If > you can pass this token to the

Re: DRI2 Protocol Spec Draft

2008-09-10 Thread Kristian Høgsberg
On Wed, Sep 10, 2008 at 5:10 PM, Keith Packard <[EMAIL PROTECTED]> wrote: > On Wed, 2008-09-10 at 14:09 -0400, Kristian Høgsberg wrote: > >> Everybody can talk to the DRM and create >> a token, but only if you can pass it to the server over DRI2 protocol, >> can you authenticate. > > Oh, so the coo

Re: DRI2 Protocol Spec Draft

2008-09-10 Thread Keith Packard
On Wed, 2008-09-10 at 14:09 -0400, Kristian Høgsberg wrote: > Everybody can talk to the DRM and create > a token, but only if you can pass it to the server over DRI2 protocol, > can you authenticate. Oh, so the cookie in the protocol is a client identifier of some kind. In any case, 32 bits of u

Re: DRI2 Protocol Spec Draft

2008-09-10 Thread Keith Packard
On Wed, 2008-09-10 at 11:54 -0400, Kristian Høgsberg wrote: > The buffer types available? This is for when you want to check if, > say, a DRI2_BUFFER_YUV is available, and if not fall back to something > else? I was thinking of the direct rendering libraries which it knows about, but yeah, the a

Re: DRI2 Protocol Spec Draft

2008-09-10 Thread Kristian Høgsberg
On Tue, Sep 9, 2008 at 1:34 PM, Michel Dänzer <[EMAIL PROTECTED]> wrote: > On Tue, 2008-09-09 at 10:11 -0700, Keith Packard wrote: >> On Tue, 2008-09-09 at 18:41 +0200, Michel Dänzer wrote: >> > Generally, if DRI2CopyRegion seriously wants to be useful for >> > synchronization purposes, it probably

Re: DRI2 Protocol Spec Draft

2008-09-10 Thread Kristian Høgsberg
On Tue, Sep 9, 2008 at 11:46 AM, Keith Packard <[EMAIL PROTECTED]> wrote: > On Tue, 2008-09-09 at 13:27 +0200, Michel Dänzer wrote: > >> 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

Re: DRI2 Protocol Spec Draft

2008-09-10 Thread Kristian Høgsberg
On Mon, Sep 8, 2008 at 9:38 PM, Keith Packard <[EMAIL PROTECTED]> wrote: > On Mon, 2008-09-08 at 17:58 -0400, Kristian Høgsberg wrote: >> Hi, >> >> 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 >> repla

Re: DRI2 Protocol Spec Draft

2008-09-09 Thread Stephane Marchesin
On Mon, Sep 8, 2008 at 11:58 PM, Kristian Høgsberg <[EMAIL PROTECTED]> wrote: > Hi, > > 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 mot

Re: DRI2 Protocol Spec Draft

2008-09-09 Thread Stephane Marchesin
On Tue, Sep 9, 2008 at 7:51 PM, Keith Packard <[EMAIL PROTECTED]> wrote: >> That mechanism could be basically the same as the existing >> sync-to-vblank mechanisms, but with 'vertical blank' replaced by >> 'compositing manager screen update'. So it would provide the client with >> a way to express

Re: DRI2 Protocol Spec Draft

2008-09-09 Thread Keith Packard
On Tue, 2008-09-09 at 19:34 +0200, Michel Dänzer wrote: > On Tue, 2008-09-09 at 10:11 -0700, Keith Packard wrote: > > On Tue, 2008-09-09 at 18:41 +0200, Michel Dänzer wrote: > > > > > GLX_EXT_texture_from_pixmap needs the real front buffer. > > > > Sure, but that's not through DRI2, this just ref

Re: DRI2 Protocol Spec Draft

2008-09-09 Thread Michel Dänzer
On Tue, 2008-09-09 at 10:11 -0700, Keith Packard wrote: > On Tue, 2008-09-09 at 18:41 +0200, Michel Dänzer wrote: > > > GLX_EXT_texture_from_pixmap needs the real front buffer. > > Sure, but that's not through DRI2, this just references the object as an > X pixmap. I don't understand what you me

Re: DRI2 Protocol Spec Draft

2008-09-09 Thread Keith Packard
On Tue, 2008-09-09 at 18:41 +0200, Michel Dänzer wrote: > Sounds like the DRI1 authentication mechanism. :) I don't know how DRI1 works... But, what I do want is a cookie of size sufficient to avoid any potential for security compromise. 32 bits doesn't seem like enough to me. > GLX_EXT_texture_

Re: DRI2 Protocol Spec Draft

2008-09-09 Thread Michel Dänzer
On Tue, 2008-09-09 at 12:55 -0400, Adam Jackson wrote: > On Tue, 2008-09-09 at 18:41 +0200, Michel Dänzer wrote: > > On Tue, 2008-09-09 at 08:46 -0700, Keith Packard wrote: > > > On Tue, 2008-09-09 at 13:27 +0200, Michel Dänzer wrote: > > > > I do wonder if DRI2GetBuffers should return the drawable

Re: DRI2 Protocol Spec Draft

2008-09-09 Thread Adam Jackson
On Tue, 2008-09-09 at 18:41 +0200, Michel Dänzer wrote: > On Tue, 2008-09-09 at 08:46 -0700, Keith Packard wrote: > > On Tue, 2008-09-09 at 13:27 +0200, Michel Dänzer wrote: > > > I do wonder if DRI2GetBuffers should return the drawable position > > > relative to the origin of each buffer... guess

Re: DRI2 Protocol Spec Draft

2008-09-09 Thread Michel Dänzer
On Tue, 2008-09-09 at 08:46 -0700, Keith Packard wrote: > On Tue, 2008-09-09 at 13:27 +0200, Michel Dänzer wrote: > > > 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

Re: DRI2 Protocol Spec Draft

2008-09-09 Thread Keith Packard
On Tue, 2008-09-09 at 13:27 +0200, Michel Dänzer wrote: > 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 have to admit that I'm not very excited by the ex

Re: DRI2 Protocol Spec Draft

2008-09-09 Thread Michel Dänzer
On Mon, 2008-09-08 at 17:58 -0400, Kristian Høgsberg wrote: > Hi, > > 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

Re: DRI2 Protocol Spec Draft

2008-09-08 Thread Keith Packard
On Mon, 2008-09-08 at 17:58 -0400, Kristian Høgsberg wrote: > Hi, > > 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