[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
PCI Signal Loading
- To: Mailing List Recipients <pci-sig-request@znyx.com>
- Subject: PCI Signal Loading
- From: "Scott Eichman" <seichman@simpact.com>
- Date: Fri, 30 Jan 1998 14:31:42 -0800
- Resent-Date: Fri, 30 Jan 1998 14:45:47 -0800
- Resent-From: pci-sig-request@znyx.com
- Resent-Message-ID: <"Xu5ZO2.0.7h6.OIbqq"@electra.znyx.com>
- Resent-Sender: pci-sig-request@znyx.com
I will try and make this short and sweet.
PCI spec 2.1 Signal Loading section 4.4.3.4 says:
"Shared PCI signals must be limited to one load on the expansion card.
Violation of expansion board trace . . . . ."
The section goes on to list some specific violations that must be avoided.
My question is: Do the specifics within this section apply only to the
"shared" signals identified in the first sentence? Or, do these rules also
apply to point-to-point signals?
Specificaly, can I "snoop" my own REQ# output? Am I prohibited from
connecting my own REQ#, which only goes to the system arbiter, to a CPLD
input on my own card?
If you are wondering "why the *#?@ does this idiot need to to this"? Well,
I'm using an AMCC 5933 in add-in bus mastering mode and am seeing an
extremely intermittent condition related to a known errata for the device.
The desgin error has "No Factory alteration planned" according to AMCC's
errata sheet. I think that I have a work-around that could be accomplished
by qualifying the bus master enable de-assertion, which I drive from the
board side, with the REQ# output. I would be glad to talk about it with
anyone who is really interested in the details.
Thanks in advance for any insight into section 4.4.3.4.