mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: keithp@keithp.com, airlied@linux.ie,
	Alan Hourihane <alanh@fairlite.demon.co.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dri-devel@lists.sourceforge.net
Subject: Re: i915 vsync interrupt fix
Date: Fri, 23 Jun 2006 22:25:03 -0700	[thread overview]
Message-ID: <1151126703.1668.10.camel@neko.keithp.com> (raw)
In-Reply-To: <449C891E.6010405@goop.org>

[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]

On Fri, 2006-06-23 at 17:36 -0700, Jeremy Fitzhardinge wrote:
> I need this patch from Alan Hourihane 
> <mailto:alanh@fairlite.demon.co.uk> to make direct rendering work 
> properly on my 945GM-based laptop. It comes from 
> https://bugs.freedesktop.org/show_bug.cgi?id=7233.  This change is 
> immediately useful to me now, but I don't know if the development DRM is 
> going to be merged with the kernel any time soon (I notice CVS has a 
> variant of this patch).

CVS has a more comprehensive patch where the X server tells the DRI
module which pipe it should use to signal vblank. With the patch posted,
a dual-head environment will generate interrupts on *both* pipes, which
will reduce performance while negating the desired synchronized
behaviour.

The more complete fix requires updated DRI bits and an updated
xf86-video-intel 2D driver, but no changes are needed in the Mesa GL
driver. This bumps the i915 DRM version to 1.5.

When we start looking at mergedfb environments, we may want to consider
an even more sophisticated fix where the vblank used depends on the
dominant monitor displaying the window. The patch I made won't help with
that, unfortunately.

-- 
keith.packard@intel.com

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-06-24  5:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-24  0:36 Jeremy Fitzhardinge
2006-06-24  5:25 ` Keith Packard [this message]

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=1151126703.1668.10.camel@neko.keithp.com \
    --to=keithp@keithp.com \
    --cc=airlied@linux.ie \
    --cc=alanh@fairlite.demon.co.uk \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®