Re: Vblanks, CRTCs and GLX, oh my!

2007-09-26 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michel Dänzer wrote: > On Tue, 2007-09-25 at 13:32 -0700, Jesse Barnes wrote: >> It seems that drivers that set their MSC routines to NULL will return >> GL_BAD_CONTEXT from calls like glXWaitVideoSyncSGI(), and if e.g. >> drmWaitVBlank() failed clie

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-26 Thread Kristian Høgsberg
On 9/26/07, Michel Dänzer <[EMAIL PROTECTED]> wrote: > > On Wed, 2007-09-26 at 08:31 -0700, Jesse Barnes wrote: > > On Wednesday, September 26, 2007 8:11:19 am Michel Dänzer wrote: > > > On Wed, 2007-09-26 at 07:53 -0700, Jesse Barnes wrote: > > > > On Wednesday, September 26, 2007 12:08:13 am Mich

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-26 Thread Jesse Barnes
On Wednesday, September 26, 2007 9:39 am Michel Dänzer wrote: > > Err yeah I was describing it backwards. The __DRIscreen hooks for > > the MSC stuff all point to dri_util.c wrapper functions that end up > > calling the driver hooks. However, drivers always set their hooks > > to either NULL or t

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-26 Thread Michel Dänzer
On Wed, 2007-09-26 at 08:31 -0700, Jesse Barnes wrote: > On Wednesday, September 26, 2007 8:11:19 am Michel Dänzer wrote: > > On Wed, 2007-09-26 at 07:53 -0700, Jesse Barnes wrote: > > > On Wednesday, September 26, 2007 12:08:13 am Michel Dänzer wrote: > > > > On Tue, 2007-09-25 at 13:32 -0700, Je

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-26 Thread Jesse Barnes
On Wednesday, September 26, 2007 8:11:19 am Michel Dänzer wrote: > On Wed, 2007-09-26 at 07:53 -0700, Jesse Barnes wrote: > > On Wednesday, September 26, 2007 12:08:13 am Michel Dänzer wrote: > > > On Tue, 2007-09-25 at 13:32 -0700, Jesse Barnes wrote: > > > > that moves the new fields over to the

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-26 Thread Michel Dänzer
On Wed, 2007-09-26 at 07:53 -0700, Jesse Barnes wrote: > On Wednesday, September 26, 2007 12:08:13 am Michel Dänzer wrote: > > On Tue, 2007-09-25 at 13:32 -0700, Jesse Barnes wrote: > > > > > > that moves the new fields over to the drawable private. I added a new > > > drawable hook to implement

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-26 Thread Jesse Barnes
On Wednesday, September 26, 2007 12:08:13 am Michel Dänzer wrote: > On Tue, 2007-09-25 at 13:32 -0700, Jesse Barnes wrote: > > On Monday, September 24, 2007 1:25 am Michel Dänzer wrote: > > > On Fri, 2007-09-21 at 12:46 -0700, Jesse Barnes wrote: > > > > On Friday, September 21, 2007 2:51 am Michel

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-26 Thread Michel Dänzer
On Tue, 2007-09-25 at 13:32 -0700, Jesse Barnes wrote: > On Monday, September 24, 2007 1:25 am Michel Dänzer wrote: > > On Fri, 2007-09-21 at 12:46 -0700, Jesse Barnes wrote: > > > On Friday, September 21, 2007 2:51 am Michel Dänzer wrote: > > > > > - add code to Mesa so GetMSC/WaitForMSC set > >

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-25 Thread Jesse Barnes
On Monday, September 24, 2007 1:25 am Michel Dänzer wrote: > On Fri, 2007-09-21 at 12:46 -0700, Jesse Barnes wrote: > > On Friday, September 21, 2007 2:51 am Michel Dänzer wrote: > > > > - add code to Mesa so GetMSC/WaitForMSC set > > > > DRM_VBLANK_SECONDARY correctly > > > > > > One idea (with

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-24 Thread Jesse Barnes
On Monday, September 24, 2007 1:25 am Michel Dänzer wrote: > On Fri, 2007-09-21 at 12:46 -0700, Jesse Barnes wrote: > > On Friday, September 21, 2007 2:51 am Michel Dänzer wrote: > > > > - add code to Mesa so GetMSC/WaitForMSC set > > > > DRM_VBLANK_SECONDARY correctly > > > > > > One idea (with

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-24 Thread Michel Dänzer
On Fri, 2007-09-21 at 12:46 -0700, Jesse Barnes wrote: > On Friday, September 21, 2007 2:51 am Michel Dänzer wrote: > > > - add code to Mesa so GetMSC/WaitForMSC set DRM_VBLANK_SECONDARY > > > correctly > > > > One idea (with some handwaving :) would be the common code keeping > > around a po

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-21 Thread Jesse Barnes
On Friday, September 21, 2007 2:51 am Michel Dänzer wrote: > > - add code to Mesa so GetMSC/WaitForMSC set DRM_VBLANK_SECONDARY > > correctly > > One idea (with some handwaving :) would be the common code keeping > around a pointer to the driver's vblank_flags variable or keeping > track of t

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-21 Thread Michel Dänzer
On Fri, 2007-09-21 at 07:59 -0700, Jesse Barnes wrote: > On Friday, September 21, 2007 2:51:02 am Michel Dänzer wrote: > > > So: > > > - use the vblank-rework tree to make per-CRTC vblank counters (as > > > you > > > say, this breaks some setups but will fix others) > > > > Out of curiosity,

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-21 Thread Jesse Barnes
On Friday, September 21, 2007 2:51:02 am Michel Dänzer wrote: > > So: > > - use the vblank-rework tree to make per-CRTC vblank counters (as > > you > > say, this breaks some setups but will fix others) > > Out of curiosity, what setups are you thinking of that this will fix on > its own? Can'

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-21 Thread Michel Dänzer
On Wed, 2007-09-19 at 09:59 -0700, Jesse Barnes wrote: > On Wednesday, September 19, 2007 3:52 am Michel Dänzer wrote: > > On Tue, 2007-09-18 at 14:54 -0700, Jesse Barnes wrote: > > > As it stands, DRM_IOCTL_WAIT_VBLANK is downright broken in the new > > > world of dyanmically controlled outputs an

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-19 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jesse Barnes wrote: > Both the generic DRM vblank-rework and Intel specific pipe/plane > swapping have uncovered some vblank related problems which we discussed > at XDS last week. Unfortunately, no matter what we do (including > the "do nothing" o

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-19 Thread Jesse Barnes
On Wednesday, September 19, 2007 3:52 am Michel Dänzer wrote: > On Tue, 2007-09-18 at 14:54 -0700, Jesse Barnes wrote: > > As it stands, DRM_IOCTL_WAIT_VBLANK is downright broken in the new > > world of dyanmically controlled outputs and CRTCs (at least for > > i915 and radeon): a client trying to

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-19 Thread Michel Dänzer
On Tue, 2007-09-18 at 14:54 -0700, Jesse Barnes wrote: > > As it stands, DRM_IOCTL_WAIT_VBLANK is downright broken in the new world > of dyanmically controlled outputs and CRTCs (at least for i915 and > radeon): a client trying to sync against the second CRTC that doesn't > pass _DRM_VBLANK_SE

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-19 Thread Torgeir Veimo
On 18 Sep 2007, at 22:54, Jesse Barnes wrote: Any other thoughts? Please do add the option of retrieving a serial number of the vsync irq. It is very handy when debugging video playback that suffers from judder. -- Torgeir Veimo [EMAIL PROTECTED] -

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-18 Thread Jesse Barnes
On Tuesday, September 18, 2007 3:10 pm Torgeir Veimo wrote: > On 18 Sep 2007, at 22:54, Jesse Barnes wrote: > > Any other thoughts? > > Please do add the option of retrieving a serial number of the vsync > irq. It is very handy when debugging video playback that suffers from > judder. This should

Re: Vblanks, CRTCs and GLX, oh my!

2007-09-18 Thread Keith Whitwell
Jesse Barnes wrote: > Both the generic DRM vblank-rework and Intel specific pipe/plane > swapping have uncovered some vblank related problems which we discussed > at XDS last week. Unfortunately, no matter what we do (including > the "do nothing" option), some applications will break some of th

Vblanks, CRTCs and GLX, oh my!

2007-09-18 Thread Jesse Barnes
Both the generic DRM vblank-rework and Intel specific pipe/plane swapping have uncovered some vblank related problems which we discussed at XDS last week. Unfortunately, no matter what we do (including the "do nothing" option), some applications will break some of the time in the new world ord