On Fri, 17 Nov 2017, Chris Wilson <ch...@chris-wilson.co.uk> wrote:
> That seems like a reasonably policy.
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> index 57dfaf04d819..0be79cf993fa 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@ -833,6 +833,11 @@ static void i915_workqueues_cleanup(struct
> drm_i915_private *dev_priv)
> * We don't keep the workarounds for pre-production hardware, so we expect
> our
> * driver to fail on these machines in one way or another. A little warning
> on
> * dmesg may help both the user and the bug triagers.
> + *
> + * Our policy for removing workarounds is to keep the current gen workarounds
> + * as a guide to the bring-up of the next gen (workarounds have a habit of
> + * persisting). Anything older than that should be removed along with the
> + * complications they introduce.
> */
Ack for putting that in a patch and merging.
BR,
Jani.
> static void intel_detect_preproduction_hw(struct drm_i915_private *dev_priv)
> {
>
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
