From: Erich Schubert <erich@debian.org>
To: linux-kernel@vger.kernel.org
Subject: diff NOT needed. Re: Problems with VIA Apollo Pro Chipsets
Date: Tue, 7 May 2002 00:21:25 +0200 [thread overview]
Message-ID: <20020506222125.GA2005@marvin.xmldesign.de> (raw)
In-Reply-To: <20020505112645.GA20633@marvin.xmldesign.de>
After removing one memory chip that was broken (at least memtest86 found
errors) i got rid of all errors, it seems.
So this diff is NOT needed...
The diff seemed to improve things, but i guess that was just luck...
Sorry for being too fast on that issue.
My current kernel, 2.4.19-pre7-jp10, reports the bridge now as
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
(rev 40)
So it probably isn't the known-to-be-broken one...
> --- /usr/src/linux/drivers/pci/quirks.c Mon Feb 25 20:38:03 2002
> +++ /home/erich/coding/v2.4.18/drivers/pci/quirks.c Sun May 5 12:38:07 2002
> @@ -487,6 +487,7 @@
> { PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_8363_0, quirk_vialatency },
> { PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_8371_1, quirk_vialatency },
> { PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, 0x3112 /* Not out yet ? */, quirk_vialatency },
> + { PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C598_1, quirk_vialatency },
> { PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C576, quirk_vsfx },
> { PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C597_0, quirk_viaetbf },
> { PCI_FIXUP_HEADER, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C597_0, quirk_vt82c598_id },
Gruss,
Erich Schubert
--
erich@(mucl.de|debian.org) -- GPG Key ID: 4B3A135C
A polar bear is a rectangular bear after a coordinate transform.
Die kürzeste Verbindung zwischen zwei Menschen ist ein Lächeln.
prev parent reply other threads:[~2002-05-06 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-05 11:26 Problems with VIA Apollo Pro Chipsets Erich Schubert
2002-05-06 22:21 ` Erich Schubert [this message]
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=20020506222125.GA2005@marvin.xmldesign.de \
--to=erich@debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox