From: "Souza, Jose" <jose.souza@intel.com>
To: "Roper, Matthew D" <matthew.d.roper@intel.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Ausmus, James" <james.ausmus@intel.com>
Subject: Re: [PATCH libdrm] intel: sync i915_pciids.h with kernel
Date: Mon, 16 Dec 2019 16:52:59 +0000 [thread overview]
Message-ID: <f34ba2961515a8acbd2c9169e3e1b31cdbd23fb3.camel@intel.com> (raw)
In-Reply-To: <20191212171731.GD85422@mdroper-desk1.amr.corp.intel.com>
On Thu, 2019-12-12 at 09:17 -0800, Matt Roper wrote:
> On Tue, Dec 10, 2019 at 12:06:11PM -0800, José Roberto de Souza
> wrote:
> > It is missing the new EHL/JSL PCI ids added in commit
> > 651cc835d5f6 ("drm/i915: Add new EHL/JSL PCI ids")
> >
> > Cc: James Ausmus <james.ausmus@intel.com>
> > Cc: Matt Roper <matthew.d.roper@intel.com>
> > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
>
> Matches the kernel and the bspec.
>
> Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
Thanks for the review.
I just requested libdrm commit access in the mean time could someone
push this?
Thanks
>
> > ---
> > intel/i915_pciids.h | 7 +++++--
> > 1 file changed, 5 insertions(+), 2 deletions(-)
> >
> > diff --git a/intel/i915_pciids.h b/intel/i915_pciids.h
> > index b1f66b11..3e26a917 100644
> > --- a/intel/i915_pciids.h
> > +++ b/intel/i915_pciids.h
> > @@ -579,12 +579,15 @@
> > INTEL_VGA_DEVICE(0x8A51, info), \
> > INTEL_VGA_DEVICE(0x8A5D, info)
> >
> > -/* EHL */
> > +/* EHL/JSL */
> > #define INTEL_EHL_IDS(info) \
> > INTEL_VGA_DEVICE(0x4500, info), \
> > INTEL_VGA_DEVICE(0x4571, info), \
> > INTEL_VGA_DEVICE(0x4551, info), \
> > - INTEL_VGA_DEVICE(0x4541, info)
> > + INTEL_VGA_DEVICE(0x4541, info), \
> > + INTEL_VGA_DEVICE(0x4E71, info), \
> > + INTEL_VGA_DEVICE(0x4E61, info), \
> > + INTEL_VGA_DEVICE(0x4E51, info)
> >
> > /* TGL */
> > #define INTEL_TGL_12_IDS(info) \
> > --
> > 2.24.0
> >
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-12-16 16:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 20:06 [PATCH libdrm] intel: sync i915_pciids.h with kernel José Roberto de Souza
2019-12-12 17:17 ` Matt Roper
2019-12-16 16:52 ` Souza, Jose [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-20 8:46 Adam Miszczak
2020-08-20 17:24 ` Souza, Jose
2020-06-16 12:37 ramadevi.gandi
2020-03-20 0:38 Swathi Dhanavanthri
2020-03-23 12:04 ` Timo Aaltonen
2019-08-30 20:32 Anusha Srivatsa
2019-09-05 17:54 ` Souza, Jose
2019-03-22 20:35 Anusha
2019-03-22 21:03 ` Souza, Jose
2019-03-25 10:28 ` Jani Nikula
2019-02-02 8:07 Rodrigo Vivi
2019-02-04 18:19 ` Lionel Landwerlin
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=f34ba2961515a8acbd2c9169e3e1b31cdbd23fb3.camel@intel.com \
--to=jose.souza@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=james.ausmus@intel.com \
--cc=matthew.d.roper@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).