From: Marc Lehmann <pcg@goof.com>
To: Jeff Garzik <jgarzik@mandrakesoft.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, 1 Jun 2001 22:16:37 +0200 [thread overview]
Message-ID: <20010601221637.B13797@cerebro.laendle> (raw)
In-Reply-To: <20010519110721.A1415@pua.nirvana> <20010601171848.F467@cerebro.laendle> <3B17B4B0.9A805766@mandrakesoft.com>
In-Reply-To: <3B17B4B0.9A805766@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Fri, Jun 01, 2001 at 11:28:48AM -0400
On Fri, Jun 01, 2001 at 11:28:48AM -0400, Jeff Garzik <jgarzik@mandrakesoft.com> wrote:
> 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.
Aren't PCI delayed transaction supposed to be handled by the pci master
(e.g. my northbridge), not by the (software) driver for my pdc(?) I would
also be surprised if my pdc actually used that feature, not to speak of
the fact that the promise + harddisk worked fine in another computer (the
data corruption was easily detectable, one couldn't even write 500megs
without altered bytes).
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@goof.com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
next prev parent reply other threads:[~2001-06-01 20:17 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
2001-06-01 20:16 ` Marc Lehmann [this message]
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=20010601221637.B13797@cerebro.laendle \
--to=pcg@goof.com \
--cc=Axel.Thimm@physik.fu-berlin.de \
--cc=YipingChen@via.com.tw \
--cc=doelf@au-ja.de \
--cc=info@msi-computer.de \
--cc=jgarzik@mandrakesoft.com \
--cc=john@grulic.org.ar \
--cc=linux-kernel@vger.kernel.org \
--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 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.