From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, "Zanoni,
Paulo R" <paulo.r.zanoni@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 1/3] drm/i915: Make intel_detect_preproduction_hw easier to extend
Date: Thu, 26 Jan 2017 15:45:52 +0200 [thread overview]
Message-ID: <87poja2aun.fsf@intel.com> (raw)
In-Reply-To: <20170126133545.GF19521@nuc-i3427.alporthouse.com>
On Thu, 26 Jan 2017, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Thu, Jan 26, 2017 at 03:18:28PM +0200, Jani Nikula wrote:
>> On Thu, 26 Jan 2017, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>> > As we add new generations, we should keep detecting new system
>> > development platforms that were temporarily enabled (via
>> > "i915.alpha_support") and now superseded by production systems. To make
>> > it easier to add more platforms, split the if into a series of logical
>> > operations.
>>
>> Please be careful not to conflate preproduction/early hardware with
>> alpha support in the driver. They are two distinct things. The former is
>> purely about hardware. The latter is purely about software.
>
> "temporarily enabled to facilitate development and now superseded..." ?
Yes, that's fine. A released kernel with alpha support for a given
platform will still only have alpha support for production versions of
said platform.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-01-26 13:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 12:50 [PATCH 1/3] drm/i915: Make intel_detect_preproduction_hw easier to extend Chris Wilson
2017-01-26 12:50 ` [PATCH 2/3] drm/i915: Mark the kernel as tainted if we fail the preproduction check Chris Wilson
2017-01-26 13:26 ` Jani Nikula
2017-01-26 12:50 ` [PATCH 3/3] drm/i915: Add early BXT sdv to the list of preproduction machines Chris Wilson
2017-01-26 13:02 ` [PATCH 1/3] drm/i915: Make intel_detect_preproduction_hw easier to extend Ville Syrjälä
2017-01-26 13:06 ` Paulo Zanoni
2017-01-26 13:16 ` Chris Wilson
2017-01-26 13:21 ` Chris Wilson
2017-01-26 13:18 ` Jani Nikula
2017-01-26 13:35 ` Chris Wilson
2017-01-26 13:45 ` Jani Nikula [this message]
2017-01-26 22:54 ` ✗ Fi.CI.BAT: warning for series starting with [1/3] " 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=87poja2aun.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@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;
as well as URLs for NNTP newsgroup(s).