All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Jason Gaston <jason.d.gaston@intel.com>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
	linux-pci@atrey.karlin.mff.cuni.cz, khali@linux-fr.org,
	i2c@lm-sensors.nu
Subject: Re: [PATCH 2.6.24] pci_ids: patch for Intel ICH10 DeviceID's
Date: Mon, 28 Jan 2008 17:21:33 -0700	[thread overview]
Message-ID: <20080129002133.GA13664@colo.lackof.org> (raw)
In-Reply-To: <200801281720.37350.jason.d.gaston@intel.com>

On Mon, Jan 28, 2008 at 05:20:36PM -0800, Jason Gaston wrote:
> This patch adds the Intel ICH10 LPC and SMBus Controller DeviceID's.

Jason,
two questions:
Have you submitted these to pciids.sf.net?
Where are these used in the kernel?

thanks,
grant

> 
> Signed-off-by:  Jason Gaston <jason.d.gaston@intel.com>
> 
> --- linux-2.6.24/include/linux/pci_ids.h.orig	2008-01-24 14:58:37.000000000 -0800
> +++ linux-2.6.24/include/linux/pci_ids.h	2008-01-28 15:05:41.000000000 -0800
> @@ -2339,6 +2339,12 @@
>  #define PCI_DEVICE_ID_INTEL_MCH_PC1	0x359a
>  #define PCI_DEVICE_ID_INTEL_E7525_MCH	0x359e
>  #define PCI_DEVICE_ID_INTEL_IOAT_CNB	0x360b
> +#define PCI_DEVICE_ID_INTEL_ICH10_0	0x3a14
> +#define PCI_DEVICE_ID_INTEL_ICH10_1	0x3a16
> +#define PCI_DEVICE_ID_INTEL_ICH10_2	0x3a18
> +#define PCI_DEVICE_ID_INTEL_ICH10_3	0x3a1a
> +#define PCI_DEVICE_ID_INTEL_ICH10_4	0x3a30
> +#define PCI_DEVICE_ID_INTEL_ICH10_5	0x3a60
>  #define PCI_DEVICE_ID_INTEL_IOAT_SNB	0x402f
>  #define PCI_DEVICE_ID_INTEL_IOAT_SCNB	0x65ff
>  #define PCI_DEVICE_ID_INTEL_TOLAPAI_0	0x5031

  reply	other threads:[~2008-01-29  0:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29  1:20 [PATCH 2.6.24] pci_ids: patch for Intel ICH10 DeviceID's Jason Gaston
2008-01-29  0:21 ` Grant Grundler [this message]
2008-01-29  0:37   ` Gaston, Jason D
2008-02-12  9:03 ` Jean Delvare
2008-02-12 15:26   ` Greg KH

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=20080129002133.GA13664@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=gregkh@suse.de \
    --cc=i2c@lm-sensors.nu \
    --cc=jason.d.gaston@intel.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /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.