linux-kernel - Re: 2.6.26-rc1-git1 -- trying to get vblank count for disabled pipe 0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 05 May 2008 19:59:50 +0100
From:	Steven J Newbury <steve@...wbury.org.uk>
To:	Michel Dänzer <michel@...gstengraphics.com>
Cc:	David Airlie <airlied@...ux.ie>,
	DRI for Linux <dri-devel@...ts.sourceforge.net>,
	Miles Lane <miles.lane@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.26-rc1-git1 -- trying to get vblank count for disabled
	pipe 0

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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/