On Sunday, July 20, 2008 3:46 am Michel Dänzer wrote: > On Sat, 2008-07-19 at 12:54 -0400, Robert Noland wrote: > > One other issue that I spotted while testing is that we initialize > > vblank_disable_allowed to 0. The only place that it ever becomes true > > is in post modeset. So, for me... vblanks were never getting disabled. > > Yes, that's the intention behind vblank_disable_allowed. :) It's to > prevent the interrupt from getting disabled until the display driver > calls the modeset ioctl, to prevent problems caused by the hardware > frame counter resetting to 0 with 'old' display drivers (meaning ones > that don't know to call the modeset ioctl). > > > I'm still (or again) sometimes getting the error about get_vblank_count > > being called on disabled pipe that I need to try and chase down. > > I think that's because the 3D driver is trying to sync to a pipe that > the display driver 'disabled'.
Yeah, and it's a common error. Maybe we should make the message into a DRM_DEBUG instead, or make it a little less scary. Jesse ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
