From: Brice Goglin <brice@myri.com>
To: netdev@vger.kernel.org
Subject: [PATCH 1/2] myri10ge - drop workaround for the missing AER ext cap on nVidia CK804
Date: Thu, 22 Jun 2006 21:11:59 -0400 [thread overview]
Message-ID: <20060623011158.GA18337@myri.com> (raw)
In-Reply-To: <20060623011043.GA18234@myri.com>
[PATCH] myri10ge - drop workaround for the missing AER ext cap on nVidia CK804
We don't need to hardcode the AER capability of the nVidia CK804 chipset
anymore since commit cf34a8e07f02c76f3f1232eecb681301a3d7b10b (PCI: nVidia
quirk to make AER PCI-E extended capability visible) now makes sure that
this cap will be available to pci_find_ext_capability().
Signed-off-by: Brice Goglin <brice@myri.com>
---
drivers/net/myri10ge/myri10ge.c | 6 ------
1 file changed, 6 deletions(-)
Index: linux-mm/drivers/net/myri10ge/myri10ge.c
===================================================================
--- linux-mm.orig/drivers/net/myri10ge/myri10ge.c 2006-06-22 20:41:50.000000000 -0400
+++ linux-mm/drivers/net/myri10ge/myri10ge.c 2006-06-22 20:41:59.000000000 -0400
@@ -2251,12 +2251,6 @@
}
cap = pci_find_ext_capability(bridge, PCI_EXT_CAP_ID_ERR);
- /* nvidia ext cap is not always linked in ext cap chain */
- if (!cap
- && bridge->vendor == PCI_VENDOR_ID_NVIDIA
- && bridge->device == PCI_DEVICE_ID_NVIDIA_NFORCE_CK804_PCIE)
- cap = 0x160;
-
if (!cap)
return;
next prev parent reply other threads:[~2006-06-23 1:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 1:10 [PATCH 0/2] myri10ge - drop 2 workarounds that have been fixed in the PCI core Brice Goglin
2006-06-23 1:11 ` Brice Goglin [this message]
2006-06-23 3:35 ` [PATCH 1/2] myri10ge - drop workaround for the missing AER ext cap on nVidia CK804 Jeff Garzik
2006-06-23 1:12 ` [PATCH 2/2] myri10ge - drop workaround pci_save_state() disabling MSI Brice Goglin
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=20060623011158.GA18337@myri.com \
--to=brice@myri.com \
--cc=netdev@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.