dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: ramadevi.gandi@intel.com, ashutosh.dixit@intel.com,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	ramadevi.gandi@intel.com, igt-dev@lists.freedesktop.org
Cc: kalyan.kondapally@intel.com
Subject: Re: [Intel-gfx] [PATCH libdrm] intel: sync i915_pciids.h with kernel
Date: Mon, 22 Jun 2020 18:31:24 +0300	[thread overview]
Message-ID: <87wo3znmlv.fsf@intel.com> (raw)
In-Reply-To: <20200616123758.3331-1-ramadevi.gandi@intel.com>

On Tue, 16 Jun 2020, ramadevi.gandi@intel.com wrote:
> From: Gandi Ramadevi <ramadevi.gandi@intel.com>
>
> Add DG1 PCI ID

There are no DG1 PCI IDs in kernel. So please don't add them here
either.

BR,
Jani.


>
> Signed-off-by: Gandi Ramadevi <ramadevi.gandi@intel.com>
> ---
>  intel/i915_pciids.h | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/intel/i915_pciids.h b/intel/i915_pciids.h
> index 662d8351..724e68a0 100644
> --- a/intel/i915_pciids.h
> +++ b/intel/i915_pciids.h
> @@ -605,4 +605,9 @@
>  	INTEL_VGA_DEVICE(0x9AD9, info), \
>  	INTEL_VGA_DEVICE(0x9AF8, info)
>  
> +/* DG1 */
> +#define INTEL_DG1_IDS(info) \
> +        INTEL_VGA_DEVICE(0x4905, info), \
> +        INTEL_VGA_DEVICE(0x4906, info)
> +
>  #endif /* _I915_PCIIDS_H */

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-06-22 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 12:37 [PATCH libdrm] intel: sync i915_pciids.h with kernel ramadevi.gandi
2020-06-22 15:31 ` Jani Nikula [this message]
2020-06-23 11:30   ` [igt-dev] [Intel-gfx] " Daniel Vetter

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=87wo3znmlv.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kalyan.kondapally@intel.com \
    --cc=ramadevi.gandi@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).