Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Zhenyu Wang <zhenyuw@linux.intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Fix KMS regression on Sandybridge/CPT
Date: Thu, 28 Oct 2010 10:50:04 +0100	[thread overview]
Message-ID: <0d30dc$k0jvij@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1288255088-2309-1-git-send-email-zhenyuw@linux.intel.com>

On Thu, 28 Oct 2010 16:38:08 +0800, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> We should enable FDI normal training on Sandybridge/CPT system
> as well. Also restore back some original register posting read
> that got removed. LVDS/VGA/HDMI seems back to life but DP still
> fails.

The POSTING_READs you added are no-ops since they are all followed by a
read. The transconf should have the bpc in the register at this point or
else we should have bugged much earlier. The break-exec-wait condition is
still documented for gen6, augmented with an additional break-sempahore-wait
and obviously per-ring, but this is unrelated to the changelog.

I've shrunk the patch to just the FDI portion, pushed to staging for
review.  Let's try to keep patches as minimal as possible and addressing
a single issue. (I'm as guilty of violating that as anyone.) Mostly so
that we have a clear history of why/how the code works (and I don't break
it later).
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2010-10-28  9:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28  8:38 [PATCH] drm/i915: Fix KMS regression on Sandybridge/CPT Zhenyu Wang
2010-10-28  9:50 ` Chris Wilson [this message]
2010-10-29  2:34   ` Zhenyu Wang
2010-10-29  8:52     ` Chris Wilson
2010-11-02  6:24       ` Zhenyu Wang
2010-11-04  2:23         ` Chris Wilson
     [not found]           ` <20101104055024.GJ6369@zhen-devel.sh.intel.com>
2010-11-04  6:26             ` Zhenyu Wang
2010-11-04  9:08             ` Chris Wilson

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='0d30dc$k0jvij@orsmga001.jf.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=zhenyuw@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox