From: Steven J Newbury <steve@snewbury.org.uk>
To: "Michel Dänzer" <michel@tungstengraphics.com>
Cc: David Airlie <airlied@linux.ie>,
DRI for Linux <dri-devel@lists.sourceforge.net>,
Miles Lane <miles.lane@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.26-rc1-git1 -- trying to get vblank count for disabled pipe 0
Date: Mon, 05 May 2008 19:51:10 +0100 [thread overview]
Message-ID: <1210013470.3238.6.camel@infinity> (raw)
In-Reply-To: <1209991916.24777.8.camel@infinity>
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.
next prev parent reply other threads:[~2008-05-05 19:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 1:12 2.6.26-rc1-git1 -- trying to get vblank count for disabled pipe 0 Miles Lane
2008-05-05 8:15 ` Michel Dänzer
2008-05-05 12:51 ` Steven J Newbury
2008-05-05 18:51 ` Steven J Newbury [this message]
2008-05-05 18:59 ` Steven J Newbury
2008-05-05 20:51 ` Mirco Tischler
2008-05-06 7:40 ` Michel Dänzer
2008-05-06 9:00 ` Daniel Stone
2008-05-05 18:22 ` Miles Lane
2008-05-07 5:44 ` Jesse Barnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1210013470.3238.6.camel@infinity \
--to=steve@snewbury.org.uk \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@tungstengraphics.com \
--cc=miles.lane@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.