From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Marc Lehmann <pcg@goof.com>
Cc: Axel Thimm <Axel.Thimm@physik.fu-berlin.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Au-Ja <doelf@au-ja.de>, Yiping Chen <YipingChen@via.com.tw>,
support@msi.com.tw, info@msi-computer.de, support@via-cyrix.de,
John R Lenton <john@grulic.org.ar>
Subject: Re: VIA's Southbridge bug: Latest (pseudo-)patch
Date: Fri, 01 Jun 2001 11:28:48 -0400 [thread overview]
Message-ID: <3B17B4B0.9A805766@mandrakesoft.com> (raw)
In-Reply-To: <20010519110721.A1415@pua.nirvana> <20010601171848.F467@cerebro.laendle>
Marc Lehmann wrote:
> one thing I found out using triel and error is that setting "PCI Delay
> Transaction" to enabled causes data corruption on WRITE to my ide drives
> connected to an Promise Ultra 100 PCI controlelr (I didn't get any
> corruption on the devices connected to the via ide interface, presumably
> because my bios already had the right fix).
>
> So, while the every pci master grant setting apperently fixes the internal
> via ide interface corruption the PCI Delay Transaction option also must be
> buggy (or my promise controller is) and causes data corruption at least
> with an additional promise ultra 100.
I do not mean to point fingers, but don't assume Via is at fault here.
Once you get into the area of flushing data (or not flushing, which is
what delayed txn would imply), it is entirely possible that the driver
simply does not support what occurs when the PCI Delay Txn option is
set.
--
Jeff Garzik | Disbelief, that's why you fail.
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-06-01 15:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-19 9:07 VIA's Southbridge bug: Latest (pseudo-)patch Axel Thimm
2001-05-19 16:11 ` Alan Cox
2001-05-19 20:27 ` VIA politics (was: VIA's Southbridge bug: Latest (pseudo-)patch) Axel Thimm
2001-05-20 0:44 ` VIA's Southbridge bug: Latest (pseudo-)patch Ingo Oeser
2001-05-20 19:40 ` Alan Cox
2001-05-21 17:17 ` Gerhard Mack
2001-05-21 17:25 ` Udo A. Steinberg
2001-05-21 18:21 ` Dan Hollis
2001-05-22 6:11 ` God
2001-05-22 9:10 ` Alan Cox
2001-05-21 18:19 ` Dan Hollis
2001-05-22 6:09 ` God
2001-05-19 16:42 ` Przemyslaw Wegrzyn
2001-06-01 15:18 ` Marc Lehmann
2001-06-01 15:28 ` Jeff Garzik [this message]
2001-06-01 20:16 ` Marc Lehmann
2001-06-03 22:10 ` Adrian Cox
2001-06-06 16:24 ` Marc Lehmann
2001-06-06 18:39 ` Dan Hollis
2001-06-06 16:31 ` Gérard Roudier
-- strict thread matches above, loose matches on Subject: below --
2001-05-21 17:28 Khachaturov, Vassilii
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=3B17B4B0.9A805766@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=Axel.Thimm@physik.fu-berlin.de \
--cc=YipingChen@via.com.tw \
--cc=doelf@au-ja.de \
--cc=info@msi-computer.de \
--cc=john@grulic.org.ar \
--cc=linux-kernel@vger.kernel.org \
--cc=pcg@goof.com \
--cc=support@msi.com.tw \
--cc=support@via-cyrix.de \
/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