From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915/snb: remove pre-production hardware workaround
Date: Wed, 7 Oct 2015 16:23:06 +0300 [thread overview]
Message-ID: <20151007132306.GG26517@intel.com> (raw)
In-Reply-To: <1444205866-5355-1-git-send-email-jani.nikula@intel.com>
On Wed, Oct 07, 2015 at 11:17:44AM +0300, Jani Nikula wrote:
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/i915_gem.c | 18 +-----------------
> 1 file changed, 1 insertion(+), 17 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index 52642aff1dab..1e67484fd5dc 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -4558,22 +4558,6 @@ void i915_gem_init_swizzling(struct drm_device *dev)
> BUG();
> }
>
> -static bool
> -intel_enable_blt(struct drm_device *dev)
> -{
> - if (!HAS_BLT(dev))
> - return false;
> -
> - /* The blitter was dysfunctional on early prototypes */
> - if (IS_GEN6(dev) && dev->pdev->revision < 8) {
I'm not actually sure what the revi<->stepping mapping on SNB is. My SNB
is a D2 I believe, and it has rev=0x9, so 0x8 is probably D1. I think D2
was the first production stepping, and D1 may have gotten out as
samples. So this would perhaps affect D0 and older steppings, which seems
fine to me.
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> - DRM_INFO("BLT not supported on this pre-production hardware;"
> - " graphics performance will be degraded.\n");
> - return false;
> - }
> -
> - return true;
> -}
> -
> static void init_unused_ring(struct drm_device *dev, u32 base)
> {
> struct drm_i915_private *dev_priv = dev->dev_private;
> @@ -4616,7 +4600,7 @@ int i915_gem_init_rings(struct drm_device *dev)
> goto cleanup_render_ring;
> }
>
> - if (intel_enable_blt(dev)) {
> + if (HAS_BLT(dev)) {
> ret = intel_init_blt_ring_buffer(dev);
> if (ret)
> goto cleanup_bsd_ring;
> --
> 2.1.4
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-10-07 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 8:17 [PATCH 1/3] drm/i915/snb: remove pre-production hardware workaround Jani Nikula
2015-10-07 8:17 ` [PATCH 2/3] drm/i915/vlv: " Jani Nikula
2015-10-07 13:27 ` Ville Syrjälä
2015-10-07 14:30 ` Daniel Vetter
2015-10-07 15:35 ` Ville Syrjälä
2015-10-07 8:17 ` [PATCH 3/3] drm/i915/chv: remove pre-production hardware workarounds Jani Nikula
2015-10-07 8:31 ` kbuild test robot
2015-10-07 13:28 ` Ville Syrjälä
2015-10-07 14:32 ` Daniel Vetter
2015-10-07 13:23 ` Ville Syrjälä [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=20151007132306.GG26517@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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 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.