All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Cleverdon <jamesclv@us.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH][2.6.10] Updated pci.ids for new IBM bridge
Date: Mon, 10 Jan 2005 18:42:42 -0800	[thread overview]
Message-ID: <200501101842.42267.jamesclv@us.ibm.com> (raw)

Update patch for a forthcoming bridge.

X-Signed-Off-By: James Cleverdon <jamesclv@us.ibm.com>


diff -pru 2.6.10/drivers/pci/pci.ids t10/drivers/pci/pci.ids
--- 2.6.10/drivers/pci/pci.ids	2004-12-24 13:34:57.000000000 -0800
+++ t10/drivers/pci/pci.ids	2005-01-04 16:36:28.284492825 -0800
@@ -998,6 +998,7 @@
 	0269  10/100/1000 Base-TX Ethernet Adapter (PCI-X)
 	028C  Citrine chipset SCSI controller
 		1014 02BE  Dual Channel PCI-X U320 DDR SCSI RAID Adapter (571B)
+	02a1  X-Architecture Bridge rev 3 [Summit2/EXA-32e]
 	0302  X-Architecture Bridge [Summit]
 	ffff  MPIC-2 interrupt controller
 1015  LSI Logic Corp of Canada
diff -pru 2.6.10/include/linux/pci_ids.h t10/include/linux/pci_ids.h
--- 2.6.10/include/linux/pci_ids.h	2004-12-24 13:35:50.000000000 -0800
+++ t10/include/linux/pci_ids.h	2005-01-04 18:48:11.514567375 -0800
@@ -446,7 +446,8 @@
 #define PCI_DEVICE_ID_IBM_ICOM_DEV_ID_2	0x0219
 #define PCI_DEVICE_ID_IBM_ICOM_V2_TWO_PORTS_RVX		0x021A
 #define PCI_DEVICE_ID_IBM_ICOM_V2_ONE_PORT_RVX_ONE_PORT_MDM	0x0251
-#define PCI_DEVICE_ID_IBM_ICOM_FOUR_PORT_MODEL	0x252
+#define PCI_DEVICE_ID_IBM_ICOM_FOUR_PORT_MODEL	0x0252
+#define PCI_DEVICE_ID_IBM_PCI_BRIDGE_SUMMIT2	0x02a1
 
 #define PCI_VENDOR_ID_COMPEX2		0x101a // pci.ids says "AT&T GIS (NCR)"
 #define PCI_DEVICE_ID_COMPEX2_100VG	0x0005


-- 
James Cleverdon
IBM LTC (xSeries Linux Solutions)
{jamesclv(Unix, preferred), cleverdj(Notes)} at us dot ibm dot comm

             reply	other threads:[~2005-01-11  3:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-11  2:42 James Cleverdon [this message]
2005-01-11  3:23 ` [PATCH][2.6.10] Updated pci.ids for new IBM bridge Dave Jones

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=200501101842.42267.jamesclv@us.ibm.com \
    --to=jamesclv@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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 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.