[lkml]   [2001]   [Jun]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
On Fri, Jun 01, 2001 at 11:28:48AM -0400, Jeff Garzik <> 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 +--
--==---/ / _ \/ // /\ \/ / |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:54    [W:0.100 / U:1.216 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site