All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yu Dai <yu.dai@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915/kbl: drm/i915: Avoid GuC loading for now on Kabylake.
Date: Fri, 6 Nov 2015 11:08:25 -0800	[thread overview]
Message-ID: <563CFAA9.9000903@intel.com> (raw)
In-Reply-To: <1446139321-2818-1-git-send-email-rodrigo.vivi@intel.com>



On 10/29/2015 10:22 AM, Rodrigo Vivi wrote:
> GuC has no version for KBL published yet and it is not recommended
> to load the Skylake one, so let's avoid loading this for now while
> we don't have the proper GuC firmware for Kabylake.
>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
>   drivers/gpu/drm/i915/i915_drv.h | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index a5ba485..0e971cf 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -2616,8 +2616,8 @@ struct drm_i915_cmd_table {
>   
>   #define HAS_CSR(dev)	(IS_GEN9(dev))
>   
> -#define HAS_GUC_UCODE(dev)	(IS_GEN9(dev))
> -#define HAS_GUC_SCHED(dev)	(IS_GEN9(dev))
> +#define HAS_GUC_UCODE(dev)	(IS_GEN9(dev) && !IS_KABYLAKE(dev))
> +#define HAS_GUC_SCHED(dev)	(IS_GEN9(dev) && !IS_KABYLAKE(dev))
>   
>   #define HAS_RESOURCE_STREAMER(dev) (IS_HASWELL(dev) || \
>   				    INTEL_INFO(dev)->gen >= 8)
Looks good to me.
Reviewed-by: Alex Dai <yu.dai@intel.com>

Alex
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2015-11-06 19:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 17:14 [PATCH 0/6] Kabylake patches V2 Rodrigo Vivi
2015-10-27 17:14 ` [PATCH 1/6] drm/i915: Define IS_BROXTON properly Rodrigo Vivi
2015-10-28  9:27   ` Jani Nikula
2015-10-27 17:14 ` [PATCH 2/6] drm/i915/kbl: Introduce Kabylake platform defition Rodrigo Vivi
2015-10-28 11:39   ` Jani Nikula
2015-10-28 11:16     ` [PATCH] " Rodrigo Vivi
2015-10-28 19:18       ` Jani Nikula
2015-10-28 19:31       ` Chris Wilson
2015-10-28 19:44         ` Rodrigo Vivi
2015-10-28 20:01           ` Chris Wilson
2015-10-27 17:14 ` [PATCH 3/6] drm/i915/kbl: Add Kabylake PCI ID Rodrigo Vivi
2015-10-28 19:19   ` [PATCH] " Rodrigo Vivi
2015-10-27 17:14 ` [PATCH 4/6] drm/i915/kbl: Add Kabylake GT4 " Rodrigo Vivi
2015-10-28 19:21   ` [PATCH] " Rodrigo Vivi
2015-10-28 19:49     ` Jani Nikula
2015-10-27 17:14 ` [PATCH 5/6] drm/i915/kbl: Use propper ddi buffer translation table for Kabylake ULT and ULX Rodrigo Vivi
2015-11-06 20:26   ` Paulo Zanoni
2015-10-27 17:14 ` [PATCH 6/6] drm/i915/kbl: Fix DMC load on Kabylake Rodrigo Vivi
2015-10-29 17:20   ` [PATCH] " Rodrigo Vivi
2015-10-29 17:58     ` kbuild test robot
2015-10-29 18:05     ` kbuild test robot
2015-10-29 17:22 ` [PATCH 1/2] drm/i915/kbl: drm/i915: Avoid GuC loading for now " Rodrigo Vivi
2015-10-29 17:22   ` [PATCH 2/2] drm/i915/kbl: Kabylake uses the same GMS values as Skylake Rodrigo Vivi
2015-10-29 17:53     ` kbuild test robot
2015-11-04 23:35     ` Rodrigo Vivi
2015-11-05 13:17       ` Jani Nikula
2015-10-29 20:02   ` [PATCH 1/2] drm/i915/kbl: drm/i915: Avoid GuC loading for now on Kabylake kbuild test robot
2015-11-06 19:08   ` Yu Dai [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=563CFAA9.9000903@intel.com \
    --to=yu.dai@intel.com \
    --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.