From: Chris Wilson <chris@chris-wilson.co.uk>
To: Eric Anholt <eric@anholt.net>, Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: clarify IS_GEN vs IS_<product> usage
Date: Tue, 10 May 2011 22:24:43 +0100 [thread overview]
Message-ID: <382e69$ctpctm@azsmga001.ch.intel.com> (raw)
In-Reply-To: <874o52xul9.fsf@pollan.anholt.net>
On Tue, 10 May 2011 11:45:54 -0700, Eric Anholt <eric@anholt.net> wrote:
> On Mon, 9 May 2011 11:42:13 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> This feels like a lot of churn to me, for the pre-gen4 chipsets at
> least. gen2 is always is_830_display (which is overly specific), and
> gen3 is always is_i915_display.
The argument is that we want to be consistent in how we test for
capabilities so that adding new feature tests or new chipsets is easier
and has no side-effects with existing capabilities. How the macros map
on to the actual devices is another matter - a compromise between
simplicity and runtime efficiency.
If it doesn't reduce our long term maintenance burden, then there is
no point making the distinction. I think more fine-grained checks will
help in the future, (and consistency across all generations prevents silly
bugs).
I'm still skeptical that the segregation of capabilities between
chipset/display/render is as clear cut as Jesse portrays. ;-)
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2011-05-10 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 22:16 [PATCH] drm/i915: clarify IS_GEN vs IS_<product> usage Jesse Barnes
2011-05-05 22:57 ` Chris Wilson
2011-05-09 18:42 ` Jesse Barnes
2011-05-09 19:09 ` Chris Wilson
2011-05-10 18:45 ` Eric Anholt
2011-05-10 21:24 ` Chris Wilson [this message]
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='382e69$ctpctm@azsmga001.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=eric@anholt.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
/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