From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Add i810/i815 pci-ids for completeness
Date: Mon, 13 Mar 2017 15:04:21 +0200 [thread overview]
Message-ID: <87varde3ai.fsf@intel.com> (raw)
In-Reply-To: <20170313112810.4202-1-chris@chris-wilson.co.uk>
On Mon, 13 Mar 2017, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> To improve our historical record and to simplify userspace that wants to
> include i915_pciids.h as its canonical breakdown of PCI IDs and their
> respective generations, include the gen1 ids for i810 and i815.
Is this how you start sneaking in support for them in i915? ;)
Acked-by: Jani Nikula <jani.nikula@intel.com>
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> include/drm/i915_pciids.h | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/include/drm/i915_pciids.h b/include/drm/i915_pciids.h
> index 466c71592a6f..27e0dbaa6c0e 100644
> --- a/include/drm/i915_pciids.h
> +++ b/include/drm/i915_pciids.h
> @@ -47,6 +47,14 @@
> 0x030000, 0xff0000, \
> (unsigned long) info }
>
> +#define INTEL_I810_IDS(info) \
> + INTEL_VGA_DEVICE(0x7121, info), /* I810 */ \
> + INTEL_VGA_DEVICE(0x7123, info), /* I810_DC100 */ \
> + INTEL_VGA_DEVICE(0x7125, info) /* I810_E */
> +
> +#define INTEL_I815_IDS(info) \
> + INTEL_VGA_DEVICE(0x1132, info) /* I815*/
> +
> #define INTEL_I830_IDS(info) \
> INTEL_VGA_DEVICE(0x3577, info)
--
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-03-13 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 11:28 [PATCH] drm/i915: Add i810/i815 pci-ids for completeness Chris Wilson
2017-03-13 12:53 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-03-13 13:04 ` Jani Nikula [this message]
2017-03-13 13:10 ` [PATCH] " Chris Wilson
2017-03-17 17:12 ` Chris Wilson
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=87varde3ai.fsf@intel.com \
--to=jani.nikula@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.