Re: DRM timing broken in 2.6.18

On Tue, Sep 26, 2006 at 11:30:40 +0200, Michel Dänzer wrote: On Tue, 2006-09-26 at 02:21 -0700, Keith Packard wrote: On Tue, 2006-09-26 at 10:49 +0200, Michel Dänzer wrote: Define 'too fast'. Is it just slightly off, or about twice as fast? Either way, this is most likely related to

Re: DRM timing broken in 2.6.18

I thought I made it pick only one of the pipes. Did I mess up? Your code looks fine to me, not sure how it ends up with both enabled... Is there anything I can do to give further debug info? strace the ioctl that your app is calling... see what it returns, see why it returns twice... Dave.

Re: DRM timing broken in 2.6.18

Is there anything I can do to give further debug info? strace the ioctl that your app is calling... see what it returns, see why it returns twice... Do you use intelfb (just as an aside...)? Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux

[Bug 4602] Resume from suspend to disk causes crash (suspend2)

http://bugzilla.kernel.org/show_bug.cgi?id=4602 [EMAIL PROTECTED] changed: What|Removed |Added OtherBugsDependingO||7216 nThis|