From: Dave Gordon <david.s.gordon@intel.com>
To: yu.dai@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/guc: Support GuC SKL v6.1
Date: Thu, 25 Feb 2016 14:59:34 +0000 [thread overview]
Message-ID: <56CF16D6.9090307@intel.com> (raw)
In-Reply-To: <1456332546-31050-1-git-send-email-yu.dai@intel.com>
On 24/02/16 16:49, yu.dai@intel.com wrote:
> From: Alex Dai <yu.dai@intel.com>
>
> This version of GuC firmware fixes the engine reset issue where golden
> context LRC address is treated as page index by mistake. It also fixes
> the problem that scheduler stops submiting to one engine when the other
> engine work queue is full.
>
> Signed-off-by: Alex Dai <yu.dai@intel.com>
Hi Alex,
I heard a rumour that GuC 6.1 required a change to the driver interface?
If you can confirm that this is not so, then I'm happy with this, so:
Reviewed-by: Dave Gordon <david.s.gordon@intel.com>
Also: GuC 6.1 has no known outstanding bugs to be fixed, so this would
be a really good time to enable GuC submission by default on machines
with this firmware installed. So I'm also going to repost the enabling
patch (which you already R-B'ed) as a reply to this, so they should be
taken together :)
.Dave.
> ---
> drivers/gpu/drm/i915/intel_guc_loader.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_guc_loader.c b/drivers/gpu/drm/i915/intel_guc_loader.c
> index e0093a9..e329a8a 100644
> --- a/drivers/gpu/drm/i915/intel_guc_loader.c
> +++ b/drivers/gpu/drm/i915/intel_guc_loader.c
> @@ -59,7 +59,7 @@
> *
> */
>
> -#define I915_SKL_GUC_UCODE "i915/skl_guc_ver4.bin"
> +#define I915_SKL_GUC_UCODE "i915/skl_guc_ver6.bin"
> MODULE_FIRMWARE(I915_SKL_GUC_UCODE);
>
> /* User-friendly representation of an enum */
> @@ -611,8 +611,8 @@ void intel_guc_ucode_init(struct drm_device *dev)
> fw_path = NULL;
> } else if (IS_SKYLAKE(dev)) {
> fw_path = I915_SKL_GUC_UCODE;
> - guc_fw->guc_fw_major_wanted = 4;
> - guc_fw->guc_fw_minor_wanted = 3;
> + guc_fw->guc_fw_major_wanted = 6;
> + guc_fw->guc_fw_minor_wanted = 1;
> } else {
> fw_path = ""; /* unknown device */
> }
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-02-25 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 16:49 [PATCH] drm/i915/guc: Support GuC SKL v6.1 yu.dai
2016-02-25 14:59 ` Dave Gordon [this message]
2016-02-25 16:50 ` Yu Dai
2016-02-25 16:53 ` [PATCH] drm/i915: add enable_guc_loading parameter Dave Gordon
2016-02-25 17:32 ` ✗ Fi.CI.BAT: warning for drm/i915: add enable_guc_loading parameter (rev2) Patchwork
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=56CF16D6.9090307@intel.com \
--to=david.s.gordon@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=yu.dai@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;
as well as URLs for NNTP newsgroup(s).