public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915/cnl: Remove alpha_support protection
Date: Wed, 14 Feb 2018 18:17:30 +0200	[thread overview]
Message-ID: <87y3jvk0kl.fsf@intel.com> (raw)
In-Reply-To: <20180214155840.13666-1-rodrigo.vivi@intel.com>

On Wed, 14 Feb 2018, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> We now have a stable cnl on our CI and it seems mostly
> green without big risks of blank screen or anything
> blowing up on linux installations in the future.
>
> As a reminder i915.alpha_support was created to protect
> future linux instalation's iso images that might contain a kernel
> from the enabling time of the new platform. Without this
> protection most of linux installation was recommending
> nomodeset option during installation that was getting stick
> there after installation.

Specifically, alpha support says nothing about the development state of
the hardware, and everything about the state of the driver in a kernel
release.

This is semantically no different from the old preliminary_hw_support
flag, but the old one was all too often interpreted as (preliminary hw)
support instead of the intended (preliminary) hw support, and it was
misleading for everyone. Hence the rename.

Please fix the typos, and with that,

Acked-by: Jani Nikula <jani.nikula@intel.com>

>
> Reference: https://intel-gfx-ci.01.org/tree/drm-tip/fi-cnl-y3.html
> Cc: James Ausmus <james.ausmus@intel.com>
> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> Cc: Jani Saarinen <jani.saarinen@intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_pci.c | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c
> index 4e7a10c89782..49cef20594b3 100644
> --- a/drivers/gpu/drm/i915/i915_pci.c
> +++ b/drivers/gpu/drm/i915/i915_pci.c
> @@ -573,7 +573,6 @@ static const struct intel_device_info intel_coffeelake_gt3_info = {
>  
>  static const struct intel_device_info intel_cannonlake_info = {
>  	GEN10_FEATURES,
> -	.is_alpha_support = 1,
>  	.platform = INTEL_CANNONLAKE,
>  	.gen = 10,
>  	.gt = 2,

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-02-14 16:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 15:58 [PATCH] drm/i915/cnl: Remove alpha_support protection Rodrigo Vivi
2018-02-14 16:17 ` Jani Nikula [this message]
2018-02-14 20:42   ` Rodrigo Vivi
2018-02-15 12:14     ` Joonas Lahtinen
2018-02-14 17:00 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-02-14 22:35 ` ✗ Fi.CI.BAT: failure for drm/i915/cnl: Remove alpha_support protection (rev2) Patchwork
2018-02-14 23:21 ` ✓ Fi.CI.BAT: success " Patchwork
2018-02-15  8:14 ` ✓ Fi.CI.IGT: " Patchwork
2018-02-15  9:34 ` ✗ Fi.CI.IGT: failure " 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=87y3jvk0kl.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox