On Mon, 2008-05-05 at 19:51 +0100, Steven J Newbury wrote: > On Mon, 2008-05-05 at 13:51 +0100, Steven J Newbury wrote: > > On Mon, 2008-05-05 at 10:15 +0200, Michel Dänzer wrote: > > > On Sun, 2008-05-04 at 21:12 -0400, Miles Lane wrote: > [snip] > > > Note that some of these are for pipe 1 as well as pipe 0. Does the > > > problem only occur for one of them? > > Miles isn't alone, I also get 'trying to get vblank count for disabled > > pipe 0' (GM965). vblank interrupts were previously not working for me, > > but they are now. I'm not sure what's changed. > OK I know what changed. The DRM in the kernel has working vblank but it > still produces the "disabled" warning in the kernel log. git DRM > produces ~1 fps with sync to vblank enabled. Seems the vblank interrupt > isn't getting enabled in the git DRM, but the warning message is > actually unrelated. Actually I had a patch from my previous attempt to fix this still applied to my git-drm. Now reverted git-drm is behaving identically to the linux kernel DRM. vsync is working but the disabled pipe warning is produced.
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
