public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: remove indirection in the PCI ID macros
Date: Tue, 03 Feb 2015 15:05:05 +0200	[thread overview]
Message-ID: <87zj8vxi0u.fsf@intel.com> (raw)
In-Reply-To: <20150203123928.GF26272@nuc-i3427.alporthouse.com>

On Tue, 03 Feb 2015, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Tue, Feb 03, 2015 at 02:34:05PM +0200, Jani Nikula wrote:
>> Spell all the PCI IDs out to be able to quickly grep for the IDs. No
>> functional changes.
>
> On the other hand this is a loss of contextual information in the header
> file.

I assume the GT count is what you're referring to. I contemplated that,
and decided that I, personally, really value the file as the canonical
place to look at all the supported PCI IDs above all.

Also, I'm pretty sure there's nothing in the specs that make guarantees
about digits in PCI IDs mapping to GT count. My impression is that it's
just an inference on our part, valid for the set of PCI IDs currently in
the file. But this isn't that important.

BR,
Jani.


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

  reply	other threads:[~2015-02-03 13:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03 12:34 [PATCH] drm/i915: remove indirection in the PCI ID macros Jani Nikula
2015-02-03 12:39 ` Chris Wilson
2015-02-03 13:05   ` Jani Nikula [this message]
2015-02-03 13:14     ` Chris Wilson
2015-02-03 13:36 ` Damien Lespiau
2015-02-03 13:40   ` Chris Wilson
2015-03-11 16:08   ` Daniel Vetter
2015-02-03 17:51 ` shuang.he

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=87zj8vxi0u.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.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