From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Fix offset page-flips on i965+
Date: Sun, 08 Aug 2010 12:39:00 +0100 [thread overview]
Message-ID: <89k83a$974h4e@azsmga001.ch.intel.com> (raw)
In-Reply-To: <1281259225-23421-1-git-send-email-chris@chris-wilson.co.uk>
On Sun, 8 Aug 2010 10:20:25 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> OUT_RING(MI_DISPLAY_FLIP |
> MI_DISPLAY_FLIP_PLANE(intel_crtc->plane));
> - OUT_RING(fb->pitch);
> - OUT_RING(offset | obj_priv->tiling_mode);
> - pipesrc = I915_READ(pipesrc_reg);
> - OUT_RING(pipesrc & 0x0fff0fff);
> + OUT_RING(fb->pitch | obj_priv->tiling_mode);
> + /* i965+ uses the linear or tiled offsets from the
> + * Display Registers (which do not change across a page-flip)
> + * so we need only reprogram the base address.
> + */
> + OUT_RING(obj_priv->gtt_offset);
There's a discrepancy here between our internal docs and the publish PDFs
for MI_DISPLAY_FLIP. In our docs, we have pitch | tiling. In the
PDF, it's address | tiling. There are other inconsistencies in the
bitfields surround this in the PDF, so it is worth a second set of eyes
checking this.
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-08-08 11:39 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 [this message]
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
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='89k83a$974h4e@azsmga001.ch.intel.com' \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox