From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: torvalds@transmeta.com, davej@suse.de, linux-kernel@vger.kernel.org
Subject: PATCH: 2.5.27 pci quirk for dunord
Date: Sun, 21 Jul 2002 21:19:41 +0100 (BST) [thread overview]
Message-ID: <E17WNB7-0007Zp-00@the-village.bc.nu> (raw)
diff -u --new-file --recursive --exclude-from /usr/src/exclude linux-2.5.27/drivers/pci/quirks.c linux-2.5.27-ac1/drivers/pci/quirks.c
--- linux-2.5.27/drivers/pci/quirks.c Sat Jul 20 20:11:05 2002
+++ linux-2.5.27-ac1/drivers/pci/quirks.c Sun Jul 21 19:43:26 2002
@@ -457,10 +457,26 @@
}
/*
+ * DreamWorks provided workaround for Dunord I-3000 problem
+ *
+ * This card decodes and responds to addresses not apparently
+ * assigned to it. We force a larger allocation to ensure that
+ * nothing gets put too close to it.
+ */
+
+static void __init quirk_dunord ( struct pci_dev * dev )
+{
+ struct resource * r = & dev -> resource [ 1 ];
+ r -> start = 0;
+ r -> end = 0xffffff;
+}
+
+/*
* The main table of quirks.
*/
static struct pci_fixup pci_fixups[] __initdata = {
+ { PCI_FIXUP_HEADER, PCI_VENDOR_ID_DUNORD, PCI_DEVICE_ID_DUNORD_I3000, quirk_dunord },
{ PCI_FIXUP_FINAL, PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82441, quirk_passive_release },
{ PCI_FIXUP_FINAL, PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82441, quirk_passive_release },
/*
diff -u --new-file --recursive --exclude-from /usr/src/exclude linux-2.5.27/include/linux/pci_ids.h linux-2.5.27-ac1/include/linux/pci_ids.h
--- linux-2.5.27/include/linux/pci_ids.h Sat Jul 20 20:11:14 2002
+++ linux-2.5.27-ac1/include/linux/pci_ids.h Sun Jul 21 19:44:09 2002
@@ -1611,6 +1611,9 @@
#define PCI_DEVICE_ID_DCI_PCCOM4 0x0001
#define PCI_DEVICE_ID_DCI_PCCOM8 0x0002
+#define PCI_VENDOR_ID_DUNORD 0x5544
+#define PCI_DEVICE_ID_DUNORD_I3000 0x0001
+
#define PCI_VENDOR_ID_GENROCO 0x5555
#define PCI_DEVICE_ID_GENROCO_HFP832 0x0003
reply other threads:[~2002-07-21 19:52 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=E17WNB7-0007Zp-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).