From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Fix offset page-flips on i965+
Date: Wed, 11 Aug 2010 08:18:57 -0700 [thread overview]
Message-ID: <20100811081857.5bbf82c6@virtuousgeek.org> (raw)
In-Reply-To: <1281518747-5085-2-git-send-email-chris@chris-wilson.co.uk>
On Wed, 11 Aug 2010 10:25:47 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:
> i965 uses the Display Registers to compute the offset from the display
> base so the new base does not need adjusting when flipping. The older
> chipsets use a fence to access the display and so do perceive the
> surface as linear and have a single base register which is reprogrammed
> using the flip.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> Reported-by: Marty Jack <martyj19@comcast.net>
> ---
> drivers/gpu/drm/i915/intel_display.c | 67 ++++++++++++++++++++++++----------
> 1 files changed, 48 insertions(+), 19 deletions(-)
Looks good. Marty, any chance you could reply with a tested-by?
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2010-08-11 15:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C5E04F9.5010005@comcast.net>
2010-08-08 9:20 ` [PATCH] drm/i915: Fix offset page-flips on i965+ Chris Wilson
2010-08-08 11:39 ` Chris Wilson
2010-08-08 12:24 ` Daniel Vetter
2010-08-08 14:50 ` Daniel Vetter
2010-08-08 11:50 ` [PATCH] drm/i915: gen4 vs gen5 DISPLAY_FLIP discrepancy? Chris Wilson
2010-08-10 21:37 ` [PATCH] drm/i915: Fix offset page-flips on i965+ Jesse Barnes
2010-08-11 9:25 ` [PATCH 1/2] drm/i915: Include a generation number in the device info Chris Wilson
2010-08-11 14:14 ` Adam Jackson
2010-08-11 14:29 ` Chris Wilson
2010-08-11 9:25 ` [PATCH 2/2] drm/i915: Fix offset page-flips on i965+ Chris Wilson
2010-08-11 15:18 ` Jesse Barnes [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=20100811081857.5bbf82c6@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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 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.