From: "peerchen" <peerchen@gmail.com>
To: "linux-kernel" <linux-kernel@vger.kernel.org>
Cc: "akpm" <akpm@linux-foundation.org>, "pchen" <pchen@nvidia.com>,
"acurrid" <acurrid@nvidia.com>
Subject: [PATCH 2/2] msi: set 'En' bit of MSI Mapping Capability on HT platform
Date: Sun, 25 Nov 2007 11:24:22 +0800 [thread overview]
Message-ID: <200711251124187655098@gmail.com> (raw)
According to the HyperTransport spec, 'En' indicate if the MSI Mapping is active. So it should be set when enable the MSI.
The patch base on kernel 2.6.24-rc3
Signed-off-by: Andy Currid <acurrid@nvidia.com>
Signed-off-by: Peer Chen <pchen@nvidia.com>
---
--- linux-2.6.24-rc3/include/linux/pci_ids.h.orig 2007-11-23 17:50:30.000000000 -0500
+++ linux-2.6.24-rc3/include/linux/pci_ids.h 2007-11-23 17:50:42.000000000 -0500
@@ -1153,7 +1153,16 @@
#define PCI_DEVICE_ID_NVIDIA_NFORCE_MCP51_IDE 0x0265
#define PCI_DEVICE_ID_NVIDIA_NFORCE_MCP51_SATA 0x0266
#define PCI_DEVICE_ID_NVIDIA_NFORCE_MCP51_SATA2 0x0267
+#define PCI_DEVICE_ID_NVIDIA_NFORCE_C51_MEMC0 0x02F0
+#define PCI_DEVICE_ID_NVIDIA_NFORCE_C51_MEMC1 0x02F1
+#define PCI_DEVICE_ID_NVIDIA_NFORCE_C51_MEMC2 0x02F2
+#define PCI_DEVICE_ID_NVIDIA_NFORCE_C51_MEMC3 0x02F3
+#define PCI_DEVICE_ID_NVIDIA_NFORCE_C51_MEMC4 0x02F4
+#define PCI_DEVICE_ID_NVIDIA_NFORCE_C51_MEMC5 0x02F5
+#define PCI_DEVICE_ID_NVIDIA_NFORCE_C51_MEMC6 0x02F6
+#define PCI_DEVICE_ID_NVIDIA_NFORCE_C51_MEMC7 0x02F7
#define PCI_DEVICE_ID_NVIDIA_NFORCE_MCP55_SMBUS 0x0368
+#define PCI_DEVICE_ID_NVIDIA_NFORCE_MCP55_MEMC 0x0369
#define PCI_DEVICE_ID_NVIDIA_NFORCE_MCP55_IDE 0x036E
#define PCI_DEVICE_ID_NVIDIA_NFORCE_MCP55_SATA 0x037E
#define PCI_DEVICE_ID_NVIDIA_NFORCE_MCP55_SATA2 0x037F
-
reply other threads:[~2007-11-25 3:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200711251124187655098@gmail.com \
--to=peerchen@gmail.com \
--cc=acurrid@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pchen@nvidia.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 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.