From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Seth Heasley <seth.heasley@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
khali@linux-fr.org, seth.heasley@intel.com
Subject: Re: [PATCH 2.6.32.3] irq: irq and pci_ids patch for Intel Cougar Point DeviceIDs
Date: Fri, 15 Jan 2010 10:23:20 -0800 [thread overview]
Message-ID: <20100115102320.4020b5cf@jbarnes-piketon> (raw)
In-Reply-To: <201001121656.37664.seth.heasley@intel.com>
On Tue, 12 Jan 2010 16:56:37 -0800
Seth Heasley <seth.heasley@intel.com> wrote:
> This patch adds the Intel Cougar Point (PCH) LPC and SMBus Controller
> DeviceIDs.
>
> Signed-off-by: Seth Heasley <seth.heasley@intel.com>
>
> --- linux-2.6.32.3/arch/x86/pci/irq.c.orig 2010-01-06
> 15:07:45.000000000 -0800 +++ linux-2.6.32.3/arch/x86/pci/irq.c
> 2010-01-07 13:10:28.000000000 -0800 @@ -590,6 +590,8 @@
> case PCI_DEVICE_ID_INTEL_ICH10_1:
> case PCI_DEVICE_ID_INTEL_ICH10_2:
> case PCI_DEVICE_ID_INTEL_ICH10_3:
> + case PCI_DEVICE_ID_INTEL_CPT_LPC1:
> + case PCI_DEVICE_ID_INTEL_CPT_LPC2:
> r->name = "PIIX/ICH";
> r->get = pirq_piix_get;
> r->set = pirq_piix_set;
> --- linux-2.6.32.3/include/linux/pci_ids.h.orig 2010-01-06
> 15:07:45.000000000 -0800 +++
> linux-2.6.32.3/include/linux/pci_ids.h 2010-01-07
> 13:10:28.000000000 -0800 @@ -2398,6 +2398,9 @@ #define
> PCI_DEVICE_ID_INTEL_82840_HB 0x1a21 #define
> PCI_DEVICE_ID_INTEL_82845_HB 0x1a30 #define
> PCI_DEVICE_ID_INTEL_IOAT 0x1a38 +#define
> PCI_DEVICE_ID_INTEL_CPT_SMBUS 0x1c22 +#define
> PCI_DEVICE_ID_INTEL_CPT_LPC1 0x1c42 +#define
> PCI_DEVICE_ID_INTEL_CPT_LPC2 0x1c43 #define
> PCI_DEVICE_ID_INTEL_82801AA_0 0x2410 #define
> PCI_DEVICE_ID_INTEL_82801AA_1 0x2411 #define
> PCI_DEVICE_ID_INTEL_82801AA_3 0x2413
>
Applied to my linux-next branch, thanks.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2010-01-15 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 0:56 Seth Heasley
2010-01-15 18:23 ` Jesse Barnes [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=20100115102320.4020b5cf@jbarnes-piketon \
--to=jbarnes@virtuousgeek.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=seth.heasley@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
all inboxes | Powered by JetHome®