From: Oliver Feiler <kiza@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: pci/quirks.c - VIA PCI latency in 2.4.4
Date: Mon, 30 Apr 2001 15:19:05 +0200 [thread overview]
Message-ID: <20010430151905.A12136@munich.netsurf.de> (raw)
Hi,
pci/quirks.c in Linux 2.4.4 contains the latency patch for the VIA
686B southbridge. However the line 315 in the file reads:
{ PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_8363_0
, quirk_vialatency },
Doesn't this only activate the patch on KT133 boards and not on AMD760
boards for example that use the 686B southbridge as well? So shouldn't be
PCI_DEVICE_ID_VIA_82C686 (I don't know the correct ID for the 686B chip)
placed there instead? Is this correct?
Bye
Oliver
--
Oliver Feiler kiza@gmx.net
http://www.lionking.org/~kiza/pgpkey PGP key ID: 0x561D4FD2
http://www.lionking.org/~kiza/
next reply other threads:[~2001-04-30 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-30 13:19 Oliver Feiler [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-30 13:48 pci/quirks.c - VIA PCI latency in 2.4.4 Charl P. Botha
2001-04-30 13:58 ` Charl P. Botha
2001-04-30 14:33 ` Alan Cox
2001-04-30 15:39 ` Charl P. Botha
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=20010430151905.A12136@munich.netsurf.de \
--to=kiza@gmx.net \
--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