From: Daniel Vetter <daniel@ffwll.ch>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915/kbl: Remove preliminary_hw_support protection from Kabylake.
Date: Thu, 7 Jan 2016 10:30:33 +0100 [thread overview]
Message-ID: <20160107093033.GK8076@phenom.ffwll.local> (raw)
In-Reply-To: <1452129330-3484-3-git-send-email-rodrigo.vivi@intel.com>
On Wed, Jan 06, 2016 at 05:15:30PM -0800, Rodrigo Vivi wrote:
> The only missing gap compared to Skylake is the GuC
> because we don't have yet a GuC firmware image to publish.
>
> However with all other parts in place this is very similar to
> Skylake which is out of this procection.
>
> So I'm now confident that Kabylake is in a good stage and won't
> cause troubles like blank displays, hard hangs, etc.
>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Imo we should have at least 1 kbl in CI before doing this. Do we have
that?
-Daniel
> ---
> drivers/gpu/drm/i915/i915_drv.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> index 3ac616d..c8ddf3e 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@ -346,14 +346,12 @@ static const struct intel_device_info intel_broxton_info = {
>
> static const struct intel_device_info intel_kabylake_info = {
> HSW_FEATURES,
> - .is_preliminary = 1,
> .is_kabylake = 1,
> .gen = 9,
> };
>
> static const struct intel_device_info intel_kabylake_gt3_info = {
> HSW_FEATURES,
> - .is_preliminary = 1,
> .is_kabylake = 1,
> .gen = 9,
> .ring_mask = RENDER_RING | BSD_RING | BLT_RING | VEBOX_RING | BSD2_RING,
> --
> 2.4.3
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-01-07 9:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 1:15 [PATCH 1/3] drm/i915/kbl: Adding missing IS_KABYLAKE checks Rodrigo Vivi
2016-01-07 1:15 ` [PATCH 2/3] drm/i915: Don't warn if the workaround list is empty part 2 Rodrigo Vivi
2016-01-08 0:49 ` Rodrigo Vivi
2016-01-07 1:15 ` [PATCH 3/3] drm/i915/kbl: Remove preliminary_hw_support protection from Kabylake Rodrigo Vivi
2016-01-07 9:30 ` Daniel Vetter [this message]
2016-01-07 16:14 ` [PATCH 1/3] drm/i915/kbl: Adding missing IS_KABYLAKE checks Michel Thierry
2016-01-08 0:32 ` Vivi, Rodrigo
2016-01-08 0:49 ` [PATCH] " Rodrigo Vivi
2016-02-26 0:23 ` Rodrigo Vivi
2016-02-29 14:35 ` Jani Nikula
2016-03-16 14:31 ` Michel Thierry
2016-03-16 15:15 ` Jani Nikula
2016-03-16 15:32 ` Daniel Vetter
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=20160107093033.GK8076@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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.