From: "John Shriver" <jshriver@linuxmail.org>
To: linux-kernel@vger.kernel.org
Subject: 2.4.19-rc1 still has one issue with Intel D845GBV motherboard
Date: Thu, 04 Jul 2002 00:29:29 +0400 [thread overview]
Message-ID: <20020703202929.27339.qmail@linuxmail.org> (raw)
Most of the patches necessary to get the IDE controller in the ICH4 (82801DB) on the Intel D845GBV motherboard are already in 2.4.19-rc1. (These are the issues in the mail thread "Anthony Spinillo" <tspinillo@linuxmail.org> started on June 1, 2002.)
However, the patch to pci-pc.c that JeffN sent him is still needed, as the BIOS on the board (both patches P02 and P04) doesn't allocate any I/O space for the first four BAR's in the IDE device.
So this is confirmation that such a patch is needed, and that JeffN's patch works. I suspect it's generic to all Intel BIOSes that are setting up the ICH4.
I've attached a fresh version of the patch based on the 2.4.19-rc1 baseline.
--- linux/arch/i386/kernel/pci-pc.c.orig 2002-07-03 15:48:46.000000000 -0400
+++ linux/arch/i386/kernel/pci-pc.c 2002-07-03 15:50:19.000000000 -0400
@@ -1250,6 +1250,7 @@
{ PCI_FIXUP_HEADER, PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82454GX, pci_fixup_i450gx },
{ PCI_FIXUP_HEADER, PCI_VENDOR_ID_UMC, PCI_DEVICE_ID_UMC_UM8886BF, pci_fixup_umc_ide },
{ PCI_FIXUP_HEADER, PCI_VENDOR_ID_SI, PCI_DEVICE_ID_SI_5513, pci_fixup_ide_trash },
+ { PCI_FIXUP_HEADER, PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82801DB_11, pci_fixup_ide_trash },
{ PCI_FIXUP_HEADER, PCI_ANY_ID, PCI_ANY_ID, pci_fixup_ide_bases },
{ PCI_FIXUP_HEADER, PCI_VENDOR_ID_SI, PCI_DEVICE_ID_SI_5597, pci_fixup_latency },
{ PCI_FIXUP_HEADER, PCI_VENDOR_ID_SI, PCI_DEVICE_ID_SI_5598, pci_fixup_latency },
--
Get your free email from www.linuxmail.org
Powered by Outblaze
reply other threads:[~2002-07-03 20:27 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=20020703202929.27339.qmail@linuxmail.org \
--to=jshriver@linuxmail.org \
--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.