[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Strange failure with PLX9060ES
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: RE: Strange failure with PLX9060ES
- From: David Griffin <daveg@highwater.co.uk>
- Date: Mon, 12 May 1997 13:57:20 +0100
- In-Reply-To: <01BC5ECD.7BC13EE0@penthouse>
- Resent-Date: Mon, 12 May 1997 13:57:20 +0100
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-Id: <"bsDz81.0.Tz1.b2yTp"@dart>
- Resent-Sender: pci-sig-request@znyx.com
Adam,
thanks for the reply, but I don't understand how the motherboard chipset
can be involved at this stage. It is clearly related to the problem
(perhaps it was the termination of the previous transaction which caused
the problem ?, but it looked fine on the analyser), but I'm not sure how
the m/b chipset can prevent the PLX from issuing a REQ signal in response
to an ADS on it's local bus side.
Am I missing something ?
Dave
>With reference to David Griffin's problem (original message appended) :
>
>I think you're hitting a problem with the Triton 430FX chipset associated
with peer-to-peer DMA. The chipset's arbiter locks up in various
circumstances when you attempt this; I saw this a year or so ago using a
PLX PCI9060 (not ES) to write directly to a DCI display, and posted a
question at that time, which got me a response that suggested that the old
hands on this mailing list are well aware of this problem. Note that DMA
to/from host memory is fine so your SCSI card or whatever will work OK.
>
>It would appear that when Intel's marketing people invented the phrase
"concurrent PCI" to describe the capabilities of their newer PCIsets they
actually meant "PCI which works".
>
>Adam Barnes
>Transtech Parallel Systems
>
>
z Ì »