From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/7] drm/i915: automatic FDI training support for Ivy Bridge
Date: Wed, 27 Apr 2011 07:19:52 +0100 [thread overview]
Message-ID: <849307$cmdqsq@azsmga001.ch.intel.com> (raw)
In-Reply-To: <20110426170601.48fe675b@jbarnes-desktop>
On Tue, 26 Apr 2011 17:06:01 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> You can ignore this set; I only sent it because I thought the others
> wouldn't come through.
Before I find the others... Do they treat IS_IVYBRIDGE() vs IS_GEN7
consistently? Do they have sufficient debug and self-tests?
Can we split intel_enable_clock_gating() up into several "little"
functions that address the peculiarity of each generation individually?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-04-27 6:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 23:51 [PATCH 1/7] drm/i915: automatic FDI training support for Ivy Bridge Jesse Barnes
2011-04-26 23:51 ` [PATCH 2/7] drm/i915: manual FDI training " Jesse Barnes
2011-04-26 23:51 ` [PATCH 3/7] drm/i915: treat Ivy Bridge watermarks like Sandy Bridge Jesse Barnes
2011-04-26 23:51 ` [PATCH 4/7] drm/i915: interrupt & vblank support for Ivy Bridge Jesse Barnes
2011-04-26 23:51 ` [PATCH 5/7] drm/i915: page flip " Jesse Barnes
2011-04-26 23:51 ` [PATCH 6/7] drm/i915: untested DP " Jesse Barnes
2011-04-26 23:51 ` [PATCH 7/7] drm/i915: ring " Jesse Barnes
2011-04-27 0:06 ` [PATCH 1/7] drm/i915: automatic FDI training " Jesse Barnes
2011-04-27 6:19 ` Chris Wilson [this message]
2011-04-27 20:52 ` 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='849307$cmdqsq@azsmga001.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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.