From: Jiri Kosina <jkosina@suse.cz>
To: Greg KH <greg@kroah.com>, Ayaz Abdulla <aabdulla@nvidia.com>
Cc: jgarzik@pobox.com, linux-pci@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org
Subject: [PATCH] PCI: nVidia's MCP61 ethernet card needs quirk for wrong class
Date: Mon, 1 Oct 2007 16:20:46 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710011615390.7567@jikos.suse.cz> (raw)
From: Jiri Kosina <jkosina@suse.cz>
PCI: nVidia's MCP61 ethernet card needs quirk for wrong class
The MCP61 ethernet controller from nVidia (NVENET_19) contains wrong
PCI class:
00:07.0 Bridge [0680]: nVidia Corporation MCP61 Ethernet [10de:03ef] (rev a2)
i.e. it identifies itself as a bridge. Fix this.
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index 50f2dd9..fbf6a89 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -1511,6 +1511,13 @@ static void __devinit fixup_rev1_53c810(struct pci_dev* dev)
}
DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_NCR, PCI_DEVICE_ID_NCR_53C810, fixup_rev1_53c810);
+/* nVidia's MCP61 ethernet card has wrong PCI class (0x0680) */
+static void __devinit fixup_nvenet_19(struct pci_dev *dev)
+{
+ dev->class = PCI_CLASS_NETWORK_ETHERNET << 8;
+}
+DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_NVIDIA, PCI_DEVICE_ID_NVIDIA_NVENET_19, fixup_nvenet_19);
+
static void pci_do_fixups(struct pci_dev *dev, struct pci_fixup *f, struct pci_fixup *end)
{
while (f < end) {
next reply other threads:[~2007-10-01 14:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 14:20 Jiri Kosina [this message]
2007-10-01 14:46 ` [PATCH] PCI: nVidia's MCP61 ethernet card needs quirk for wrong class Jeff Garzik
2007-10-01 14:50 ` Jiri Kosina
2007-10-01 14:54 ` Jeff Garzik
2007-10-01 15:01 ` Jiri Kosina
2007-10-01 15:10 ` Jeff Garzik
2007-10-01 15:24 ` Jiri Kosina
2007-10-01 16:25 ` Greg KH
2007-10-01 17:03 ` Matthew Wilcox
2007-10-01 17:15 ` 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=Pine.LNX.4.64.0710011615390.7567@jikos.suse.cz \
--to=jkosina@suse.cz \
--cc=aabdulla@nvidia.com \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--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 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).