From: "Souza, Jose" <jose.souza@intel.com>
To: "Srivatsa, Anusha" <anusha.srivatsa@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/ehl: Add new PCI ids
Date: Mon, 6 Jul 2020 17:12:08 +0000 [thread overview]
Message-ID: <7ce99f07592db6db8ccc80d996166619cfc9ee6f.camel@intel.com> (raw)
In-Reply-To: <83F5C7385F545743AD4FB2A62F75B0734C6BDE9F@ORSMSX107.amr.corp.intel.com>
On Fri, 2020-07-03 at 03:00 -0700, Srivatsa, Anusha wrote:
> > -----Original Message-----
> > From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of José
> > Roberto de Souza
> > Sent: Tuesday, June 30, 2020 1:36 AM
> > To: intel-gfx@lists.freedesktop.org
> > Subject: [Intel-gfx] [PATCH] drm/i915/ehl: Add new PCI ids
> >
> > Two new PCI ids added to ehl.
> >
> > BSpec: 29153
> > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > ---
> > include/drm/i915_pciids.h | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/include/drm/i915_pciids.h b/include/drm/i915_pciids.h index
> > bc989de2aac2..0c7fcb1632ac 100644
> > --- a/include/drm/i915_pciids.h
> > +++ b/include/drm/i915_pciids.h
> > @@ -588,6 +588,8 @@
> > INTEL_VGA_DEVICE(0x4551, info), \
> > INTEL_VGA_DEVICE(0x4541, info), \
> > INTEL_VGA_DEVICE(0x4E71, info), \
> > + INTEL_VGA_DEVICE(0x4557, info), \
> > + INTEL_VGA_DEVICE(0x4555, info), \
> > INTEL_VGA_DEVICE(0x4E61, info), \
> > INTEL_VGA_DEVICE(0x4E51, info)
>
> There are more PCIIDs missing from this patch. Like 0x4571,0x4551 etc
0x4551 is right above and 0x4571 is above that but out from this diff: https://cgit.freedesktop.org/drm-tip/tree/include/drm/i915_pciids.h
>
> Anusha
> > --
> > 2.27.0
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2020-07-06 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 20:06 [Intel-gfx] [PATCH] drm/i915/ehl: Add new PCI ids José Roberto de Souza
2020-06-30 12:46 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-06-30 14:37 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-07-03 10:00 ` [Intel-gfx] [PATCH] " Srivatsa, Anusha
2020-07-06 17:12 ` Souza, Jose [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=7ce99f07592db6db8ccc80d996166619cfc9ee6f.camel@intel.com \
--to=jose.souza@intel.com \
--cc=anusha.srivatsa@intel.com \
--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